Triple
T27392316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kouvola |
E691571
|
entity |
| Predicate | municipalityMergerYear |
P176
|
FINISHED |
| Object | 2009 |
—
|
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 | Statement: [Kouvola, municipalityMergerYear, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalityMergerYear Context triple: [Kouvola, municipalityMergerYear, 2009]
-
A.
partOfMunicipalitySince
Indicates that an entity has been included within and administratively belonging to a specific municipality starting from a given point in time.
-
B.
hadMunicipalitiesUntil2006
Indicates that an entity possessed or was composed of specific municipalities up until the year 2006, after which this municipal structure or association changed or ceased.
-
C.
incorporatedAsMunicipalityBy
Indicates that an entity was formally established and given municipal status through official action by another governing body or authority.
-
D.
mergerYear
chosen
Indicates the year in which two or more entities formally merged into a single entity.
-
E.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 12:26 p.m.