Triple

T27384118
Position Surface form Disambiguated ID Type / Status
Subject Runway 34 E691317 entity
Predicate orientationAffectedBy P38251 FINISHED
Object local magnetic variation 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: local magnetic variation | Statement: [Runway 34, orientationAffectedBy, local magnetic variation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: orientationAffectedBy
Context triple: [Runway 34, orientationAffectedBy, local magnetic variation]
  • A. orientationType
    Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
  • B. orientationInducedBy chosen
    Indicates that the orientation of one entity is determined or caused by the orientation or configuration of another entity.
  • C. orientationProperty
    Indicates that one entity has a specific spatial or directional orientation in relation to another entity or reference frame.
  • D. orientedFrom
    Indicates that one entity has a defined direction or orientation starting at or determined by another reference entity.
  • E. orientationException
    Indicates an exception or deviation from the normal or expected orientation relationship between entities.
  • 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_69ef520386788190bc92cfcd97ebb67a completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62cd2ceb481908cd9fae52a542206 completed May 2, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69f62c1762f881908c25e8f70ecd5041 completed May 2, 2026, 4:53 p.m.
Created at: April 27, 2026, 12:23 p.m.