Triple
T4392541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | non-Hodgkin lymphoma |
E99398
|
entity |
| Predicate | hasTypicalSymptom |
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: [non-Hodgkin lymphoma, hasTypicalSymptom, painless lymphadenopathy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalSymptom Context triple: [non-Hodgkin lymphoma, hasTypicalSymptom, painless lymphadenopathy]
-
A.
symptom
chosen
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
B.
hasHealthConcern
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
-
C.
symptomAssociatedWithInfection
Indicates that a particular symptom is linked to, or commonly occurs as a result of, a specific infection.
-
D.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
E.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35285592881909fcdea225a655950 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.