Triple
T4392564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | non-Hodgkin lymphoma |
E99398
|
entity |
| Predicate | isDiagnosedBy |
P52059
|
FINISHED |
| Object | lymph node biopsy |
—
|
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: lymph node biopsy | Statement: [non-Hodgkin lymphoma, isDiagnosedBy, lymph node biopsy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDiagnosedBy Context triple: [non-Hodgkin lymphoma, isDiagnosedBy, lymph node biopsy]
-
A.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
B.
diagnosisMethod
chosen
Indicates the method, procedure, or technique used to establish or confirm a diagnosis for a condition or case.
-
C.
diagnoses
Indicates that a medical professional identifies and determines the nature or cause of a condition, disease, or problem in a patient.
-
D.
diagnosisYear
Indicates the calendar year in which a diagnosis was made or recorded for an entity.
-
E.
mayBeComorbidWith
Indicates that two conditions or disorders can occur together in the same individual, potentially influencing each other’s presence or severity.
- 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.