Triple
T6609969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 07/25 |
E149211
|
entity |
| Predicate | hasApproximateHeading |
P72427
|
FINISHED |
| Object | 070 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: 070 degrees | Statement: [Runway 07/25, hasApproximateHeading, 070 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateHeading Context triple: [Runway 07/25, hasApproximateHeading, 070 degrees]
-
A.
hasApproachHeading
Indicates that an entity follows or is aligned with a specified heading or direction when making an approach.
-
B.
hasApproximateCoordinates
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
C.
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.
-
D.
hasRelationToTrueHeading
Indicates that an entity has a specified relationship or correspondence to a true (reference) heading or direction.
-
E.
hasReciprocalMagneticHeadingApprox
Indicates that two entities have magnetic headings that are approximately reciprocal (differing by about 180 degrees from each other).
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cf3796d08190a26e988386089447 |
completed | March 27, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69c6acfed25481909cac74c84a9fe088 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6cf3683d08190b19e2aad30f2800f |
completed | March 27, 2026, 6:40 p.m. |
Created at: March 27, 2026, 1:57 p.m.