Triple
T35367559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NS |
E1021674
|
entity |
| Predicate | associatedCityPopulationRange |
P144473
|
FINISHED |
| Object | over 200000 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 200000 inhabitants | Statement: [NS, associatedCityPopulationRange, over 200000 inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCityPopulationRange Context triple: [NS, associatedCityPopulationRange, over 200000 inhabitants]
-
A.
associatedCityPopulationRole
Indicates a relationship where an entity is linked to a city specifically in terms of that city's population-related role, status, or function.
-
B.
populationRange
Indicates the numerical interval within which the size of a population falls.
-
C.
cityPopulationContext
Indicates the contextual relationship between a city and information about its population, such as size, distribution, or demographic characteristics.
-
D.
homeCityPopulationGroup
chosen
Indicates that an entity’s home city belongs to a specified population size category or range.
-
E.
corePopulationOf
Indicates that one entity is the primary or central population associated with, or constituting the main inhabitants of, another entity.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.