Triple
T20072816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinaburg |
E499780
|
entity |
| Predicate | presentDayCityPopulationOver |
P43438
|
FINISHED |
| Object | 80000 |
—
|
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: 80000 | Statement: [Dinaburg, presentDayCityPopulationOver, 80000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayCityPopulationOver Context triple: [Dinaburg, presentDayCityPopulationOver, 80000]
-
A.
currentPopulation
Indicates the present number of individuals living in or belonging to a specified entity (such as a location or group).
-
B.
cityPopulationContext
Indicates the contextual relationship between a city and information about its population, such as size, distribution, or demographic characteristics.
-
C.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
D.
modernPopulationCenters
Indicates that the related entities are contemporary, significant population hubs where large numbers of people currently live and concentrate.
-
E.
hasPopulationOver
chosen
Indicates that one entity has a population greater than a specified number or than 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e664392c748190a6cc472f80b8c74b |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.