Triple
T32271686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | diphtheria |
E824428
|
entity |
| Predicate | affectedSystem |
P32380
|
FINISHED |
| Object | respiratory system |
—
|
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: respiratory system | Statement: [diphtheria, affectedSystem, respiratory system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedSystem Context triple: [diphtheria, affectedSystem, respiratory system]
-
A.
affectedComponent
Indicates that one entity is a component that is impacted or influenced by another entity or event.
-
B.
associatedSystem
chosen
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
C.
effectOnSystem
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
-
D.
affectedProvision
Indicates that a particular legal provision is impacted, modified, or influenced by another action, decision, or provision.
-
E.
affectedEntity
Indicates that an entity is the one that is impacted, influenced, or acted upon as a result of an event, action, or process.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 12:42 a.m.