Triple
T5160972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hodgkin lymphoma |
E116434
|
entity |
| Predicate | commonSymptom |
P2896
|
FINISHED |
| Object | painless lymphadenopathy |
—
|
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: painless lymphadenopathy | Statement: [Hodgkin lymphoma, commonSymptom, painless lymphadenopathy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSymptom Context triple: [Hodgkin lymphoma, commonSymptom, painless lymphadenopathy]
-
A.
symptom
chosen
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
B.
symptomAssociatedWithInfection
Indicates that a particular symptom is linked to, or commonly occurs as a result of, a specific infection.
-
C.
hasPossibleSymptom
Indicates that an entity (such as a condition or disease) may be associated with a particular symptom that can potentially occur.
-
D.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
E.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79073a54819080cd1e8de6fe906a |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.