Triple
T20062038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiikala |
E499499
|
entity |
| Predicate | subdivisionTypeBeforeMerger |
P98304
|
FINISHED |
| Object | municipality |
—
|
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: municipality | Statement: [Kiikala, subdivisionTypeBeforeMerger, municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionTypeBeforeMerger Context triple: [Kiikala, subdivisionTypeBeforeMerger, municipality]
-
A.
censusSubdivisionTypeBeforeMerger
chosen
Indicates the type or classification of a census subdivision that it held prior to being merged into another administrative unit.
-
B.
subdivisionType0
Indicates that the referenced entity is classified as the primary (level 0) type of administrative or territorial subdivision within a larger jurisdiction.
-
C.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
D.
subdividedBy
Indicates that something is divided into smaller parts or sections by another entity or criterion.
-
E.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66376f2d4819081b9e1b265650e5b |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.