Triple
T12707898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onsøy |
E303635
|
entity |
| Predicate | populationAsOf1993 |
P5555
|
FINISHED |
| Object | approximately 12000 |
—
|
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 12000 | Statement: [Onsøy, populationAsOf1993, approximately 12000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationAsOf1993 Context triple: [Onsøy, populationAsOf1993, approximately 12000]
-
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.
hostsPopulation
Indicates that an entity serves as the living environment or container in which a particular population exists or resides.
-
D.
populationDemonym
Indicates the term used to refer to the people or inhabitants associated with a particular place or region.
-
E.
hasPopulationOver
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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9620663e881908d367170ed6d2c81 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.