Triple
T24931613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic Finnic peoples |
E619001
|
entity |
| Predicate | havePopulationCentersIn |
P70368
|
FINISHED |
| Object | Sweden |
—
|
NE NERFINISHED |
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: Sweden | Statement: [Baltic Finnic peoples, havePopulationCentersIn, Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: havePopulationCentersIn Context triple: [Baltic Finnic peoples, havePopulationCentersIn, Sweden]
-
A.
hasPopulationCenter
Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
-
B.
hasPopulationCenterType
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
C.
modernPopulationCenters
Indicates that the related entities are contemporary, significant population hubs where large numbers of people currently live and concentrate.
-
D.
hasPopulationConcentrationIn
chosen
Indicates that a population is densely or significantly clustered within a specified geographic area or region.
-
E.
notablePopulationCenter
Indicates that a location is recognized as a significant or prominent center of population within a given area or context.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:30 a.m.