Triple

T31712640
Position Surface form Disambiguated ID Type / Status
Subject CCAir E809367 entity
Predicate parentCarrierRelationship P189351 FINISHED
Object regional affiliate of US Airways 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: regional affiliate of US Airways | Statement: [CCAir, parentCarrierRelationship, regional affiliate of US Airways]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: parentCarrierRelationship
Context triple: [CCAir, parentCarrierRelationship, regional affiliate of US Airways]
  • A. parentRelationship
    Indicates a familial relationship in which one entity is the parent of another entity.
  • B. fareRelationship
    Indicates a relationship between entities based on the cost, pricing, or fare charged for a service or trip.
  • C. fareControlRelationship
    Indicates a relationship where one entity manages, enforces, or oversees the collection, validation, or regulation of fares for another entity or system.
  • D. intendedCarrier
    Indicates that one entity is designated or planned to serve as the carrier or transporter of another entity.
  • E. referralRelationship
    Indicates a relationship in which one entity directs or recommends another entity to a third party for services, information, or further action.
  • F. None of above. chosen

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_69f348df4e048190a4a5a9932ada78d6 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fbbc49da8c8190902bbb05d2477cab completed May 6, 2026, 10:10 p.m.
PD Predicate disambiguation batch_69fbb13f34b08190bbbb220ac1e6e666 completed May 6, 2026, 9:23 p.m.
PDg Predicate description generation batch_69fbbc48b75c8190bec27dd4b7de797f completed May 6, 2026, 10:10 p.m.
Created at: April 30, 2026, 11:16 p.m.