Triple
T19934255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norrtälje |
E479132
|
entity |
| Predicate | populationAsOf2010 |
P108649
|
FINISHED |
| Object | about 19000 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 19000 inhabitants | Statement: [Norrtälje, populationAsOf2010, about 19000 inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationAsOf2010 Context triple: [Norrtälje, populationAsOf2010, about 19000 inhabitants]
-
A.
populationTotal2010
chosen
Indicates the total number of individuals in a population as measured or recorded for the year 2010.
-
B.
rankInUS2010Census
Indicates the numerical position of an entity in the ranking of occurrences within the 2010 United States Census.
-
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.
staffPopulationApprox
Indicates an approximate or estimated number of staff associated with an entity.
-
E.
lastKnownPopulations
Indicates the most recently recorded population counts associated with an entity or set of entities.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a1553348190a6c4004d3f9a57c5 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.