Triple

T14229391
Position Surface form Disambiguated ID Type / Status
Subject LTU International E352710 entity
Predicate operatedShortHaul P27736 FINISHED
Object true 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: true | Statement: [LTU International, operatedShortHaul, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatedShortHaul
Context triple: [LTU International, operatedShortHaul, true]
  • A. operatesShortHaulRoutes chosen
    Indicates that an entity (such as an airline or transport operator) runs or provides short-distance routes or services.
  • B. operatesLongHaulRouteFrom
    Indicates that an entity (typically a transportation carrier) runs long-distance routes originating from a specified location.
  • C. operatesFeederFlightsFor
    Indicates that one airline or carrier runs connecting or short-haul feeder flights on behalf of, or in support of, another airline’s main services.
  • D. operatedCharterFlights
    Indicates that an entity conducted or managed charter flight services for another entity or purpose.
  • E. operatesAsRegionalCarrierFor
    Indicates that one transportation company functions as a regional carrier on behalf of another, typically providing local or feeder services under the larger company’s brand or network.
  • 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_69d8278adc7c8190a9218d69bce3c4e6 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de622b89fc8190af08dab9e1976759 completed April 14, 2026, 3:50 p.m.
PD Predicate disambiguation batch_69de05bf069c8190b69f00f00f5eb126 completed April 14, 2026, 9:15 a.m.
Created at: April 10, 2026, 1:07 a.m.