Triple
T3382104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virchow's node |
E71208
|
entity |
| Predicate | physicalExamFinding |
P39927
|
FINISHED |
| Object | palpable firm lymph node above left clavicle |
—
|
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: palpable firm lymph node above left clavicle | Statement: [Virchow's node, physicalExamFinding, palpable firm lymph node above left clavicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicalExamFinding Context triple: [Virchow's node, physicalExamFinding, palpable firm lymph node above left clavicle]
-
A.
featuresDisease
Indicates that an entity exhibits, presents, or is characterized by a particular disease.
-
B.
confirmedFinding
Indicates that a finding or observation has been verified as true or accurate, rather than being tentative or suspected.
-
C.
notableFinding
chosen
Indicates that an observation, result, or piece of evidence is considered significant or noteworthy in the given context.
-
D.
symptom
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
E.
anatomicalFeature
Indicates that one entity is an anatomical part, structure, or feature of 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5e9af608190bfb228ef99a87bb7 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.