Triple
T9769010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einthoven triangle |
E237070
|
entity |
| Predicate | leadIIIOrientation |
P42939
|
FINISHED |
| Object | from left arm to left leg |
—
|
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: from left arm to left leg | Statement: [Einthoven triangle, leadIIIOrientation, from left arm to left leg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadIIIOrientation Context triple: [Einthoven triangle, leadIIIOrientation, from left arm to left leg]
-
A.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
-
B.
orientationInducedBy
Indicates that the orientation of one entity is determined or caused by the orientation or configuration of another entity.
-
C.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
-
D.
orientationOfCross
Indicates the spatial orientation or alignment of a cross relative to a reference frame or object.
-
E.
lineOrientation
chosen
Indicates the directional alignment or angle of a line relative to a reference frame or axis.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f0c64c81908f3435dd49c0218b |
completed | April 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.