Triple
T3444634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komi ASSR |
E72645
|
entity |
| Predicate | populationMajorityInUrbanCenters |
P14328
|
FINISHED |
| Object | Russians |
—
|
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: Russians | Statement: [Komi ASSR, populationMajorityInUrbanCenters, Russians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationMajorityInUrbanCenters Context triple: [Komi ASSR, populationMajorityInUrbanCenters, Russians]
-
A.
statusInUrbanAreas
Indicates the condition, prevalence, or situation of something specifically within urban areas.
-
B.
populationConcentration
Indicates the degree to which a population is densely gathered or distributed within a specific area or region.
-
C.
majorPopulationIn
chosen
Indicates that a significant portion of a population is located in or primarily associated with a particular place or region.
-
D.
urbanizationLevel
Indicates the degree to which an area or population is characterized by urban development, infrastructure, and density of human settlement.
-
E.
majorPopulationCenter
Indicates that a location functions as a primary hub of population concentration and activity within a region.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba2b93dc819094e9cca1a5d9540a |
completed | March 8, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.