Triple
T8789124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salo, Finland |
E209115
|
entity |
| Predicate | mergedMunicipalitiesOn |
P80558
|
FINISHED |
| Object | 2009-01-01 |
—
|
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: 2009-01-01 | Statement: [Salo, Finland, mergedMunicipalitiesOn, 2009-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedMunicipalitiesOn Context triple: [Salo, Finland, mergedMunicipalitiesOn, 2009-01-01]
-
A.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
B.
hasMunicipalConsolidationWith
chosen
Indicates that two or more municipalities have been officially merged or unified into a single administrative entity or structure.
-
C.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
D.
mergedColonies
Indicates that two or more previously separate colonies have been combined into a single unified colony.
-
E.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8b0c108190af53d4bb9b132c5c |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:43 p.m.