Triple
T30869882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Georgian |
E786306
|
entity |
| Predicate | successorOperatorOnRoutes |
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: [Air Georgian, successorOperatorOnRoutes, Jazz Aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorOperatorOnRoutes Context triple: [Air Georgian, successorOperatorOnRoutes, Jazz Aviation]
-
A.
successorOnRoute
Indicates that one entity directly follows another in sequence along a specified route.
-
B.
majorSuccessorRoute
Indicates that one route is the primary or main successor to another route in a sequence or network of routes.
-
C.
successorOperator
chosen
Indicates that one operator directly follows another in a defined sequence or ordering.
-
D.
routeOperator
Indicates that an agent operates, manages, or is responsible for running a particular route or service path.
-
E.
successorConnector
Indicates a relationship where one element is directly connected to and follows another in a sequence or ordered structure.
- 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_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
Created at: April 29, 2026, 8:47 p.m.