Triple
T34675549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSC Kurumoch International Airport |
E890484
|
entity |
| Predicate | hasIataAirportOperated |
P87841
|
FINISHED |
| Object | KUF |
—
|
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: KUF | Statement: [JSC Kurumoch International Airport, hasIataAirportOperated, KUF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIataAirportOperated Context triple: [JSC Kurumoch International Airport, hasIataAirportOperated, KUF]
-
A.
operatedUnderIATACode
chosen
Indicates that an entity conducts its operations using the specified IATA (International Air Transport Association) code.
-
B.
servesAsPrimaryAirportOperatorForCity
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
-
C.
operatedForAirline
Indicates that an aircraft or flight was operated on behalf of, or under the branding of, a particular airline.
-
D.
airLegOperatedBy
Indicates that a specific segment (leg) of an air journey is operated by a particular airline or carrier.
-
E.
airlineOperationsType
Indicates the type or category of operational activities an airline conducts (e.g., passenger, cargo, charter, or mixed services).
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f723231a8c81909e3adda5cf2662e5 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.