Triple
T1684994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMT Division |
E36421
|
entity |
| Predicate | managesComplication |
P24566
|
FINISHED |
| Object | infection in immunocompromised patients |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: infection in immunocompromised patients | Statement: [BMT Division, managesComplication, infection in immunocompromised patients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesComplication Context triple: [BMT Division, managesComplication, infection in immunocompromised patients]
-
A.
hasComplication
chosen
Indicates that an entity is associated with a problem, difficulty, or adverse outcome arising as a consequence of another condition, action, or process.
-
B.
complication
Indicates that one event, action, or condition makes another more difficult, problematic, or introduces an additional obstacle or entanglement in the situation.
-
C.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
D.
managedAct
Indicates that one entity oversaw, directed, or was responsible for carrying out a particular action or activity.
-
E.
managingCenter
Indicates that one entity serves as the administrative or coordinating center responsible for managing another entity or activity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.