Triple
T33000165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USDD |
E844342
|
entity |
| Predicate | icaoCodeForAirport |
P419
|
FINISHED |
| Object | Salekhard Airport |
—
|
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: Salekhard Airport | Statement: [USDD, icaoCodeForAirport, Salekhard Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: icaoCodeForAirport Context triple: [USDD, icaoCodeForAirport, Salekhard Airport]
-
A.
airportCodeFAA
Indicates that an airport is identified by a specific FAA (Federal Aviation Administration) airport code.
-
B.
icaoCodeType
Indicates that the relationship specifies or classifies the ICAO (International Civil Aviation Organization) code associated with an entity.
-
C.
airportCodeContext
Indicates that an airport code is being used or interpreted within a specific contextual framework (such as a region, system, or standard) that defines its meaning.
-
D.
ICAOcode
chosen
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
E.
airfieldCode
Indicates that an entity is identified by a specific airfield code used to uniquely reference that airfield.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d272f31c819082d519f2cb96d8cc |
completed | May 3, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:22 a.m.