Triple
T22198924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mouhijärvi |
E548621
|
entity |
| Predicate | hasMergerContext |
P61481
|
FINISHED |
| Object | municipal consolidation in Finland |
—
|
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: municipal consolidation in Finland | Statement: [Mouhijärvi, hasMergerContext, municipal consolidation in Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMergerContext Context triple: [Mouhijärvi, hasMergerContext, municipal consolidation in Finland]
-
A.
hasMerger
Indicates a relationship where two or more entities combine into a single entity through a merger event.
-
B.
participatedInMergerContext
chosen
Indicates that an entity took part in a specific merger event or merger-related context.
-
C.
mergerImplemented
Indicates that a planned merger between entities has been fully executed and put into effect.
-
D.
precededByMerger
Indicates that one entity existed or occurred before another as a result of a merger that led to the latter entity.
-
E.
hasOwnerBeforeMerger
Indicates that an entity had a particular owner prior to a merger event taking place.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae98808819081582a57bca6312b |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.