Triple

T360983
Position Surface form Disambiguated ID Type / Status
Subject T5 E7849 entity
Predicate isMajorTerminalFor P1179 FINISHED
Object British Airways long-haul flights 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: British Airways long-haul flights | Statement: [T5, isMajorTerminalFor, British Airways long-haul flights]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMajorTerminalFor
Context triple: [T5, isMajorTerminalFor, British Airways long-haul flights]
  • A. isMajorIndexOf
    Indicates that one entity serves as the primary or major index reference for locating, organizing, or identifying another entity.
  • B. isMajorRouteFor chosen
    Indicates that something serves as a primary or heavily used pathway or channel for the movement or flow of something else.
  • C. hasMajorPort
    Indicates that a location possesses a primary, significant seaport used for major commercial or transportation activities.
  • D. otherMajorTerminal
    Indicates that an entity is associated with a different primary terminal or endpoint than the one currently referenced or considered.
  • E. isDestinationFor
    Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
  • 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_69a2e7e880008190a6ad7e06e5d03007 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ebce64c88190a0a8edcc7095f78b completed Feb. 28, 2026, 1:21 p.m.
PD Predicate disambiguation batch_69a2e95aeed48190b5e48865cc964938 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.