Triple
T31558165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dnipro Metro |
E805183
|
entity |
| Predicate | cityPopulationServed |
P79065
|
FINISHED |
| Object | over 900000 inhabitants |
—
|
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: over 900000 inhabitants | Statement: [Dnipro Metro, cityPopulationServed, over 900000 inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityPopulationServed Context triple: [Dnipro Metro, cityPopulationServed, over 900000 inhabitants]
-
A.
staffPopulationApprox
Indicates an approximate or estimated number of staff associated with an entity.
-
B.
corePopulationOf
Indicates that one entity is the primary or central population associated with, or constituting the main inhabitants of, another entity.
-
C.
cityPopulationContext
Indicates the contextual relationship between a city and information about its population, such as size, distribution, or demographic characteristics.
-
D.
populationTown
Indicates that a town has a specified number of inhabitants as its population.
-
E.
servesPopulationCentre
chosen
Indicates that one entity provides services or functions in support of a particular population centre.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:14 p.m.