Triple
T17928799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 35 |
E448269
|
entity |
| Predicate | hasHeadingRangeEndDegrees |
P129755
|
FINISHED |
| Object | 354 |
—
|
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: 354 | Statement: [Runway 35, hasHeadingRangeEndDegrees, 354]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadingRangeEndDegrees Context triple: [Runway 35, hasHeadingRangeEndDegrees, 354]
-
A.
isRoundedFromHeadingRange
Indicates that a value has been rounded based on a specified range of heading (direction) angles.
-
B.
hasMagneticHeadingRangeInDegrees
Indicates the range of possible magnetic heading values, measured in degrees, associated with an entity’s orientation or navigation.
-
C.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
D.
isRoundedFromHeading
Indicates that one value or measurement is the result of rounding another value that represents a heading or directional angle.
-
E.
hasRelationToTrueHeading
Indicates that an entity has a specified relationship or correspondence to a true (reference) heading or direction.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a5511a408190973cf5fa1f286a26 |
completed | April 19, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:20 a.m.