Triple

T35603148
Position Surface form Disambiguated ID Type / Status
Subject Shanxi Airlines E1028808 entity
Predicate IATAServiceType P15154 FINISHED
Object scheduled air carrier 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: scheduled air carrier | Statement: [Shanxi Airlines, IATAServiceType, scheduled air carrier]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: IATAServiceType
Context triple: [Shanxi Airlines, IATAServiceType, scheduled air carrier]
  • A. servesAirlineType
    Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
  • B. hasIATAFunction
    Indicates that an entity has a specific role, status, or function as defined by the International Air Transport Association (IATA).
  • C. airlineType chosen
    Indicates the classification or category of an airline based on its operational or service characteristics.
  • D. hasIATAcode
    Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
  • E. designatedAirlineType
    Indicates that an airline has been assigned a specific operational or classification type for a given context or service.
  • 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_69f76e0653ec81909b1b813c126c6574 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79ec411908190857785f69d6d6d7a completed May 3, 2026, 7:15 p.m.
PD Predicate disambiguation batch_69f79e4bdbcc8190be7a0d2cf8a77b64 completed May 3, 2026, 7:13 p.m.
Created at: May 3, 2026, 4:05 p.m.