Triple
T20476676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CommutAir |
E502332
|
entity |
| Predicate | airOperatorCategory |
P15155
|
FINISHED |
| Object | Part 121 air carrier (United States) |
—
|
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: Part 121 air carrier (United States) | Statement: [CommutAir, airOperatorCategory, Part 121 air carrier (United States)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airOperatorCategory Context triple: [CommutAir, airOperatorCategory, Part 121 air carrier (United States)]
-
A.
airlineCategory
chosen
Indicates the classification or type of an airline within a defined categorization system (e.g., full-service, low-cost, regional).
-
B.
airlineOperator
Indicates that one entity operates or manages airline services for another entity or in a specified context.
-
C.
airlineType
Indicates the classification or category of an airline based on its operational or service characteristics.
-
D.
aircraftOperator
Indicates that one entity operates, manages, or is responsible for the use of a particular aircraft.
-
E.
airLegOperatedBy
Indicates that a specific segment (leg) of an air journey is operated by a particular airline or carrier.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6996584648190a1a6dfcb57782b7f |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.