Triple
T8846260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Ural Yekaterinburg |
E210511
|
entity |
| Predicate | hasHomeCityPopulationCategory |
P11334
|
FINISHED |
| Object | major 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: major city | Statement: [FC Ural Yekaterinburg, hasHomeCityPopulationCategory, major city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeCityPopulationCategory Context triple: [FC Ural Yekaterinburg, hasHomeCityPopulationCategory, major city]
-
A.
hasHomeCity
Indicates that an entity’s primary or official city of residence or affiliation is a specified city.
-
B.
hasPopulationRank
Indicates the relative position of an entity in an ordered list based on the size of its population.
-
C.
hasPopulationOver
Indicates that one entity has a population greater than a specified number or than another entity.
-
D.
hasPopulationCenterType
chosen
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
E.
hasCityRank
Indicates that a city holds a particular rank or position within a defined ordering or hierarchy (such as size, importance, or administrative level).
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60a7c518819095399976148e1b9a |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:48 p.m.