Triple
T7853808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skedsmo |
E182120
|
entity |
| Predicate | hadPopulationAsOf2019 |
P5555
|
FINISHED |
| Object | about 54,000 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: about 54,000 inhabitants | Statement: [Skedsmo, hadPopulationAsOf2019, about 54,000 inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPopulationAsOf2019 Context triple: [Skedsmo, hadPopulationAsOf2019, about 54,000 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.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
D.
hasPopulationOver
Indicates that one entity has a population greater than a specified number or than another entity.
-
E.
populationDemonym
Indicates the term used to refer to the people or inhabitants associated with a particular place or 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_69ca82869ee08190b8f9040dbc2c0467 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb18ed56d481909266d862e0ae152d |
completed | March 31, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:51 p.m.