Triple

T27424934
Position Surface form Disambiguated ID Type / Status
Subject Runway 12/30 E690454 entity
Predicate magneticHeadingApproximateRunway30 P129753 FINISHED
Object 300 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: 300 degrees | Statement: [Runway 12/30, magneticHeadingApproximateRunway30, 300 degrees]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: magneticHeadingApproximateRunway30
Context triple: [Runway 12/30, magneticHeadingApproximateRunway30, 300 degrees]
  • A. runwayEndHeading
    Indicates the directional heading or bearing associated with the end of a runway, typically expressed in degrees relative to north.
  • B. hasReciprocalMagneticHeadingApprox
    Indicates that two entities have magnetic headings that are approximately reciprocal (differing by about 180 degrees from each other).
  • C. hasApproximateHeadingDegrees chosen
    Indicates that one entity’s heading or direction is approximately equal to a specified angle measured in degrees.
  • D. hasMagneticHeading
    Indicates the directional orientation of an entity relative to magnetic north, typically expressed as a magnetic compass bearing.
  • E. hasMagneticHeadingRangeInDegrees
    Indicates the range of possible magnetic heading values, measured in degrees, associated with an entity’s orientation or navigation.
  • 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_69ef52003fb48190b0f1295246182a86 completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62d53ad58819080c5227c7a729d15 completed May 2, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69f62c1762f881908c25e8f70ecd5041 completed May 2, 2026, 4:53 p.m.
Created at: April 27, 2026, 12:40 p.m.