Triple
T16952490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calan |
E411216
|
entity |
| Predicate | treatsSystem |
P125369
|
FINISHED |
| Object | cardiovascular 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: cardiovascular system | Statement: [Calan, treatsSystem, cardiovascular system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsSystem Context triple: [Calan, treatsSystem, cardiovascular system]
-
A.
treats
Indicates that one entity provides medical care or therapeutic intervention to another entity.
-
B.
treatmentOf
Indicates a relationship where one entity administers, provides, or is responsible for a therapeutic intervention directed toward another entity (typically a patient or condition).
-
C.
treatmentType
Indicates the specific kind or category of treatment applied or prescribed in relation to an entity or condition.
-
D.
APGSystemTreatment
Indicates a treatment or therapeutic intervention that is administered through or involves the APG system.
-
E.
treatment
Indicates that one entity is used as a medical or therapeutic intervention to address, manage, or cure a condition affecting another entity.
- F. None of above. chosen
Provenance (4 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0197f308190af7185fc9cc7a6e9 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.