Triple
T30869836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Regional Airlines |
E786305
|
entity |
| Predicate | successorInOperations |
P5677
|
FINISHED |
| Object | Jazz Aviation |
—
|
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: Jazz Aviation | Statement: [Sky Regional Airlines, successorInOperations, Jazz Aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInOperations Context triple: [Sky Regional Airlines, successorInOperations, Jazz Aviation]
-
A.
successorOperator
chosen
Indicates that one operator directly follows another in a defined sequence or ordering.
-
B.
successorInCommand
Indicates that one entity is designated to assume command authority immediately after another entity, typically when the latter is unavailable or their term ends.
-
C.
predecessorOperation
Indicates that one operation occurs or must be completed before another operation in a defined sequence.
-
D.
successorProcess
Indicates that one process directly follows another in a defined sequence or workflow.
-
E.
successorInProgram
Indicates that one element in a program directly follows another in the program’s execution or structural order.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: April 29, 2026, 8:47 p.m.