Triple
T19402021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nukus Airport |
E485346
|
entity |
| Predicate | servesPopulationCenterType |
P79065
|
FINISHED |
| Object | city |
—
|
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: city | Statement: [Nukus Airport, servesPopulationCenterType, city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesPopulationCenterType Context triple: [Nukus Airport, servesPopulationCenterType, city]
-
A.
servesPopulationCentre
chosen
Indicates that one entity provides services or functions in support of a particular population centre.
-
B.
hasPopulationCenterType
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
C.
appliesToPopulationCenter
Indicates that something (such as a rule, condition, or characteristic) is relevant or applicable to a specific population center (e.g., a city, town, or urban area).
-
D.
servicePopulationType
Indicates the type or category of population that a service is intended to serve or target.
-
E.
hasPopulationCenter
Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62577f808819099e74feab82b34a4 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:36 p.m.