Triple
T13572076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruovesi |
E324187
|
entity |
| Predicate | hasMunicipalityEstablished |
P23872
|
FINISHED |
| Object | 1868 |
—
|
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: 1868 | Statement: [Ruovesi, hasMunicipalityEstablished, 1868]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalityEstablished Context triple: [Ruovesi, hasMunicipalityEstablished, 1868]
-
A.
municipalityEstablished
chosen
Indicates that a municipality was officially created or founded at a specific point in time.
-
B.
hasMunicipalFormation
Indicates that an administrative or territorial unit is organized into, or associated with, a specific municipal formation as its local self-governing structure.
-
C.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
D.
hasMunicipalStatusUntil
Indicates that an entity possessed municipal status up to, but not beyond, a specified point in time.
-
E.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0106cb48190b20eb9bda131a68a |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.