Triple
T32975598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XY |
E843650
|
entity |
| Predicate | operatorAirlineSecondaryHubCity |
P94001
|
FINISHED |
| Object | Jeddah |
—
|
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: Jeddah | Statement: [XY, operatorAirlineSecondaryHubCity, Jeddah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAirlineSecondaryHubCity Context triple: [XY, operatorAirlineSecondaryHubCity, Jeddah]
-
A.
secondaryHubOfAirline
chosen
Indicates that an airport serves as a secondary operational hub for a particular airline, supporting but not replacing its primary hub activities.
-
B.
operatorSecondaryHubAirportIATA
Indicates the IATA airport code of a secondary hub airport used by the operator.
-
C.
associatedAirportPrimaryHubFor
Indicates that an airport serves as the primary hub for a particular airline or transportation operator.
-
D.
airlineHub
Indicates that a particular location (typically an airport or city) serves as a central hub or primary operational base for an airline.
-
E.
hasSecondaryAirport
Indicates that an entity is associated with an additional, typically smaller or alternative, airport beyond its primary one.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0056174c908190be99c91a70393e47 |
completed | May 10, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_6a00538e7e08819091ecd4316cd641a1 |
completed | May 10, 2026, 9:44 a.m. |
Created at: May 1, 2026, 1:22 a.m.