Triple

T33613730
Position Surface form Disambiguated ID Type / Status
Subject Vulcan to the Sky Trust E861057 entity
Predicate notableAircraftRegistration P5244 FINISHED
Object XH558 E861056 NE 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: XH558 | Statement: [Vulcan to the Sky Trust, notableAircraftRegistration, XH558]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableAircraftRegistration
Context triple: [Vulcan to the Sky Trust, notableAircraftRegistration, XH558]
  • A. aircraftRegistration chosen
    Indicates that an aircraft is assigned a specific official registration identifier or code.
  • B. notableAircraftCallsign
    Indicates that a particular aircraft is notably associated with, or commonly identified by, a specific callsign.
  • C. notableImportedAircraft
    Indicates that an entity is notably recognized for having imported a particular aircraft model or type.
  • D. notableTransportAircraft
    Indicates that the subject is a transport aircraft recognized for particular significance, such as historical importance, performance, or impact on aviation.
  • E. notableAircraftProduced
    Indicates that the subject entity has manufactured or been responsible for producing the specified aircraft, which are considered notable or significant.
  • F. None of above.

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_69f3498037c88190a4500f002b5540e0 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_6a037c8ae0248190b7e2ce4bf852c22d completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a365c63d7a48190aaff5e6b27719559 completed June 20, 2026, 9:24 a.m.
PD Predicate disambiguation batch_6a0379f505c88190ac0879ab422c3054 completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 1:41 a.m.