Triple
T7541390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 5 |
E178282
|
entity |
| Predicate | indicatesApproximateMagneticHeadingInDegrees |
P54717
|
FINISHED |
| Object | 50 |
—
|
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: 50 | Statement: [Runway 5, indicatesApproximateMagneticHeadingInDegrees, 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesApproximateMagneticHeadingInDegrees Context triple: [Runway 5, indicatesApproximateMagneticHeadingInDegrees, 50]
-
A.
hasReciprocalMagneticHeadingApprox
Indicates that two entities have magnetic headings that are approximately reciprocal (differing by about 180 degrees from each other).
-
B.
hasMagneticHeading
chosen
Indicates the directional orientation of an entity relative to magnetic north, typically expressed as a magnetic compass bearing.
-
C.
hasApproximateHeading
Indicates that one entity’s directional heading is approximately the same as another’s, within a specified tolerance.
-
D.
azimuthAccuracy
Indicates the degree of precision or allowable error in the measured or specified azimuth angle between entities.
-
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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8750f80819088ddfb7a5580b5df |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.