Triple
T9082503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irkutsk International Airport |
E217667
|
entity |
| Predicate | allowsInternationalCharters |
P63491
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Irkutsk International Airport, allowsInternationalCharters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsInternationalCharters Context triple: [Irkutsk International Airport, allowsInternationalCharters, yes]
-
A.
supportsCharterFlights
chosen
Indicates that one entity provides the capability or service of operating or accommodating charter flights for another entity.
-
B.
hasInternationalTerminal
Indicates that a transportation facility includes a terminal specifically designated for handling international arrivals and departures.
-
C.
includedCharteredCompanyTerritory
Indicates that a territory was part of, or fell within the jurisdiction of, a chartered company’s controlled area.
-
D.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
E.
operatedCharterFlights
Indicates that an entity conducted or managed charter flight services for another entity or purpose.
- 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_69ca83d7a0388190ba1af89ed7ba36f9 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc960a2760819084aab611eb1c43a9 |
completed | April 1, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:13 p.m.