Triple
T29577320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toijala |
E753476
|
entity |
| Predicate | governingMunicipalityType |
P10835
|
FINISHED |
| Object | town of Akaa |
—
|
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: town of Akaa | Statement: [Toijala, governingMunicipalityType, town of Akaa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingMunicipalityType Context triple: [Toijala, governingMunicipalityType, town of Akaa]
-
A.
isPartOfMunicipalityType
Indicates that one administrative unit or area belongs to, or is classified under, a specific type or category of municipality.
-
B.
hasMunicipalityType
chosen
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
-
C.
municipalWardType
Indicates the specific category or classification of a municipal ward within a local government or administrative structure.
-
D.
localGovernmentAreaType
Indicates the specific classification or category of a local government area within an administrative or governmental hierarchy.
-
E.
hasCityGovernmentType
Indicates the specific form or structure of municipal governance that administers a city.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: April 28, 2026, 6:04 p.m.