Triple
T25437590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesa Air Group |
E637416
|
entity |
| Predicate | hasPrimaryOperatingCompany |
P62102
|
FINISHED |
| Object | Mesa Airlines |
—
|
NE NERFINISHED |
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: Mesa Airlines | Statement: [Mesa Air Group, hasPrimaryOperatingCompany, Mesa Airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryOperatingCompany Context triple: [Mesa Air Group, hasPrimaryOperatingCompany, Mesa Airlines]
-
A.
operatedByCompany
chosen
Indicates that an entity is run, managed, or controlled by a specific company.
-
B.
operatedByCompanyHeadquarteredIn
Indicates that an entity is operated by a company whose headquarters is located in a specified place.
-
C.
hasRailTransportOperator
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
D.
operatingCompanyAbbreviation
Indicates that the object is an abbreviated or shortened form of the name of the company that operates the subject.
-
E.
alsoOperatedBy
Indicates that an entity is additionally operated or managed by another operator, alongside any primary or other operators.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 21, 2026, 2 p.m.