Triple
T19560647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Røyken |
E489438
|
entity |
| Predicate | populationApproximate_2019 |
P3412
|
FINISHED |
| Object | about 23,000 |
—
|
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 23,000 | Statement: [Røyken, populationApproximate_2019, about 23,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationApproximate_2019 Context triple: [Røyken, populationApproximate_2019, about 23,000]
-
A.
hasPopulationApproximate
chosen
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
B.
populationDemonym
Indicates the term used to refer to the people or inhabitants associated with a particular place or region.
-
C.
staffPopulationApprox
Indicates an approximate or estimated number of staff associated with an entity.
-
D.
populationMeasurementBy
Indicates that a population quantity or statistic is determined, recorded, or reported by a specified agent, method, or source.
-
E.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f7442e08190ad030151ec0a97d4 |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.