Triple
T16541959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carukia barnesi |
E401838
|
entity |
| Predicate | symptomsCaused |
P694
|
FINISHED |
| Object | severe back pain |
—
|
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: severe back pain | Statement: [Carukia barnesi, symptomsCaused, severe back pain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symptomsCaused Context triple: [Carukia barnesi, symptomsCaused, severe back pain]
-
A.
causeOfIllness
Indicates that one entity is the reason or source responsible for another entity’s illness or disease.
-
B.
viewsSymptoms
Indicates that one entity observes or examines the symptoms associated with another entity.
-
C.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
isUsedForSymptom
Indicates that something (such as a treatment, medication, or intervention) is employed to address, alleviate, or manage a particular symptom.
-
E.
symptom
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3455db6788190b929546050ea2488 |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.