Triple
T3382081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virchow's node |
E71208
|
entity |
| Predicate | laterality |
P7149
|
FINISHED |
| Object | left |
—
|
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: left | Statement: [Virchow's node, laterality, left]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterality Context triple: [Virchow's node, laterality, left]
-
A.
inferredLateralization
Indicates that the side or hemispheric orientation (e.g., left, right, bilateral) of an entity has been deduced indirectly from available information rather than observed directly.
-
B.
handedness
Indicates the preference or dominance of one hand over the other in performing actions or tasks.
-
C.
hemisphereDominance
Indicates which brain hemisphere (left or right) is functionally dominant for a given cognitive or neural process in an entity.
-
D.
side
chosen
Indicates that one entity is located at, aligned with, or associated with the lateral part or edge of another entity.
-
E.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
- 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.