Triple
T36644543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10L/28R |
E904670
|
entity |
| Predicate | hasDirectionHighEnd |
P200036
|
FINISHED |
| Object | approximately 280 degrees magnetic heading |
—
|
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: approximately 280 degrees magnetic heading | Statement: [10L/28R, hasDirectionHighEnd, approximately 280 degrees magnetic heading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionHighEnd Context triple: [10L/28R, hasDirectionHighEnd, approximately 280 degrees magnetic heading]
-
A.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
B.
hasDirectionVariant
Indicates that one entity is a directional variant or orientation-specific form of another entity.
-
C.
hasDirectionEndpoints
Indicates that a directional element is defined or bounded by specific start and end points.
-
D.
hasDirectionInName
Indicates that the entity’s name explicitly contains a directional term (e.g., north, south, east, west, or similar).
-
E.
isDirectional
Indicates that something has an inherent or assigned direction, specifying orientation or flow from one point or entity to another.
- F. None of above. chosen
Provenance (4 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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69ff6c04fa208190b1fab40a71ef923f |
completed | May 9, 2026, 5:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.