Triple
T29818084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viiala |
E757166
|
entity |
| Predicate | formedNewMunicipalityWith |
P101485
|
FINISHED |
| Object | Toijala |
—
|
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: Toijala | Statement: [Viiala, formedNewMunicipalityWith, Toijala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedNewMunicipalityWith Context triple: [Viiala, formedNewMunicipalityWith, Toijala]
-
A.
newMunicipalityName
Indicates that an entity has been assigned or is associated with a newly designated municipality name.
-
B.
formedMunicipalityWith
chosen
Indicates that two or more entities combined or were merged to create a single municipality.
-
C.
formedMunicipalityOn
Indicates that a new municipality was officially created or established on a specific date.
-
D.
reconstitutedAsMunicipality
Indicates that an entity which previously lost or changed its municipal status has been formally re-established or reorganized as a municipality.
-
E.
hasMunicipalFormation
Indicates that an administrative or territorial unit is organized into, or associated with, a specific municipal formation as its local self-governing structure.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: April 29, 2026, 5:27 p.m.