Triple
T3872165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascaris lumbricoides |
E92410
|
entity |
| Predicate | symptomAssociatedWithInfection |
P52058
|
FINISHED |
| Object | abdominal 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: abdominal pain | Statement: [Ascaris lumbricoides, symptomAssociatedWithInfection, abdominal pain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symptomAssociatedWithInfection Context triple: [Ascaris lumbricoides, symptomAssociatedWithInfection, abdominal pain]
-
A.
symptom
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
B.
lesionAssociatedWithSymptom
Indicates that a particular lesion is linked to, or occurs together with, a specific symptom.
-
C.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
D.
infectsTissue
Indicates that one entity (typically a pathogen or agent) invades and establishes itself within the tissue of another entity.
-
E.
featuresDisease
Indicates that an entity exhibits, presents, or is characterized by a particular disease.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:20 p.m.