Triple
T14061606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabriz International Airport |
E338358
|
entity |
| Predicate | isMajorAirportForRegion |
P75084
|
FINISHED |
| Object | northwestern Iran |
—
|
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: northwestern Iran | Statement: [Tabriz International Airport, isMajorAirportForRegion, northwestern Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorAirportForRegion Context triple: [Tabriz International Airport, isMajorAirportForRegion, northwestern Iran]
-
A.
isMajorRegionalAirportFor
chosen
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
-
B.
hasMajorAirport
Indicates that a location possesses at least one significant airport that serves as a primary hub for air travel in that area.
-
C.
isMajorCargoAirport
Indicates that an airport primarily handles large volumes of cargo traffic and serves as a significant freight hub.
-
D.
isMajorDomesticAirportCode
Indicates that an airport code belongs to a major domestic airport within a given country or region.
-
E.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568876308190840361dcaf10bd45 |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.