Triple
T8491604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A359 |
E200982
|
entity |
| Predicate | associatedWithAirlineOperations |
P83011
|
FINISHED |
| Object | long-haul routes |
—
|
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: long-haul routes | Statement: [A359, associatedWithAirlineOperations, long-haul routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithAirlineOperations Context triple: [A359, associatedWithAirlineOperations, long-haul routes]
-
A.
associatedWithFlight
Indicates a relationship where an entity is linked or connected to a specific flight, such as by participation, operation, or relevance.
-
B.
associatedAirlineType
Indicates a relationship where an airline is linked to a specific classification or type (e.g., carrier category or operational class).
-
C.
associatedWithIATAAirlineCode
Indicates that an entity is linked to or identified by a specific IATA airline code.
-
D.
associatedWithAirportCode
Indicates that one entity has a relationship or connection to an airport identified by a specific airport code.
-
E.
belongsToAirportOperator
Indicates that an airport or related facility is owned, managed, or operated by a specific airport operating organization.
- F. None of above. chosen
Provenance (4 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe55af3f48190a8cd64cdce0ebd4c |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.