Triple
T37891542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 08/26 |
E945153
|
entity |
| Predicate | orientationApproximateHeading |
P129753
|
FINISHED |
| Object | 080 degrees |
—
|
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: 080 degrees | Statement: [Runway 08/26, orientationApproximateHeading, 080 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orientationApproximateHeading Context triple: [Runway 08/26, orientationApproximateHeading, 080 degrees]
-
A.
hasApproximateHeadingDegrees
chosen
Indicates that one entity’s heading or direction is approximately equal to a specified angle measured in degrees.
-
B.
locationOrientation
Indicates how one entity is spatially oriented or positioned relative to a specific location or reference point.
-
C.
orientationRelativeToI90
Indicates the directional alignment or positioning of something in relation to Interstate 90 (I-90), such as being parallel, perpendicular, or at a specific angle to it.
-
D.
hasApproximateHeading
Indicates that one entity’s directional heading is approximately the same as another’s, within a specified tolerance.
-
E.
approximateDirection
Indicates that one entity is located in a general or rough directional relation (e.g., roughly north, south, etc.) relative to another entity, without specifying an exact bearing.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.