Triple
T316279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domodedovo International Airport |
E7713
|
entity |
| Predicate | WMOcode |
P9474
|
FINISHED |
| Object | 27707 |
—
|
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: 27707 | Statement: [Domodedovo International Airport, WMOcode, 27707]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WMOcode Context triple: [Domodedovo International Airport, WMOcode, 27707]
-
A.
WMO code
chosen
Indicates that an entity is associated with a specific identifier defined by the World Meteorological Organization (WMO) coding system.
-
B.
ICAOcode
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
C.
IOCCode
Indicates the standardized three-letter country or territory code assigned by the International Olympic Committee to represent a National Olympic Committee in Olympic contexts.
-
D.
hasFourLetterCode
Indicates that an entity is associated with a code consisting of exactly four characters.
-
E.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea6462148190825acc57f6d2adaf |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e943f12c8190883854aeed974260 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.