Triple
T8357214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillain–Barré syndrome |
E196711
|
entity |
| Predicate | hasTypicalTrigger |
P24442
|
FINISHED |
| Object | infection |
—
|
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 | Statement: [Guillain–Barré syndrome, hasTypicalTrigger, infection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalTrigger Context triple: [Guillain–Barré syndrome, hasTypicalTrigger, infection]
-
A.
hasTriggerType
chosen
Indicates that an event, condition, or mechanism is associated with a specific type or category of trigger that initiates it.
-
B.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
C.
usesTriggerSystem
Indicates that one entity operates or functions by means of a trigger-based mechanism or system provided or associated with another entity.
-
D.
hasTypicalSide
Indicates that one entity is the usual or characteristic side (e.g., lateral aspect) associated with another entity.
-
E.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804b57f88190907a4e4e389caf5f |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.