Triple
T3382080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virchow's node |
E71208
|
entity |
| Predicate | anatomicalStructure |
P45022
|
FINISHED |
| Object | lymph node |
—
|
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 | Statement: [Virchow's node, anatomicalStructure, lymph node]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anatomicalStructure Context triple: [Virchow's node, anatomicalStructure, lymph node]
-
A.
anatomicalFeature
chosen
Indicates that one entity is an anatomical part, structure, or feature of another entity.
-
B.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
C.
hasBodyRegion
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
D.
treatsAnatomicalSite
Indicates that an action, intervention, or agent is directed toward and intended to treat a specific anatomical site.
-
E.
limbMorphology
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
- 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.