Triple
T25437575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesa Air Group |
E637416
|
entity |
| Predicate | hasOperatingBrand |
P32898
|
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, hasOperatingBrand, Mesa Airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperatingBrand Context triple: [Mesa Air Group, hasOperatingBrand, Mesa Airlines]
-
A.
operatedByBrand
chosen
Indicates that an entity (such as a service, location, or product line) is run, managed, or controlled by a particular brand.
-
B.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
C.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
D.
hasCoreBrand
Indicates that one entity possesses, is associated with, or is defined by a primary or central brand.
-
E.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
- 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_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 2 p.m.