Triple
T15816335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maddux Air Lines |
E383486
|
entity |
| Predicate | operatedScheduledFlights |
P19814
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Maddux Air Lines, operatedScheduledFlights, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedScheduledFlights Context triple: [Maddux Air Lines, operatedScheduledFlights, yes]
-
A.
hasScheduledFlights
chosen
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
-
B.
airlineCommencedOperations
Indicates that an airline began its official flight operations or commercial services on a specific date or at a specific time.
-
C.
airlineOperationsType
Indicates the type or category of operational activities an airline conducts (e.g., passenger, cargo, charter, or mixed services).
-
D.
operatedCharterFlights
Indicates that an entity conducted or managed charter flight services for another entity or purpose.
-
E.
operationalControlOfFlights
Indicates that one entity has the authority and responsibility to manage and direct the operation of specific flights conducted by another entity.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a306a48190840adc49df2c26c5 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.