Triple
T15083385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deventer |
E360206
|
entity |
| Predicate | hasPopulationAsOf2023 |
P5555
|
FINISHED |
| Object | approximately 103000 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: approximately 103000 inhabitants | Statement: [Deventer, hasPopulationAsOf2023, approximately 103000 inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopulationAsOf2023 Context triple: [Deventer, hasPopulationAsOf2023, approximately 103000 inhabitants]
-
A.
hasPopulationAsOf
chosen
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
B.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
C.
hasPopulationOver
Indicates that one entity has a population greater than a specified number or than another entity.
-
D.
municipalityPopulation
Indicates the total number of inhabitants living within a given municipality.
-
E.
metropolitanAreaPopulationApproximate
Indicates that the predicate specifies an approximate total population size for a given metropolitan area.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0027450a48190a84588b6aaf84ebf |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:03 a.m.