Triple
T38274166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iisalmi |
E1021297
|
entity |
| Predicate | hasSubregionRole |
P202433
|
FINISHED |
| Object | center of Upper Savo sub-region |
—
|
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: center of Upper Savo sub-region | Statement: [Iisalmi, hasSubregionRole, center of Upper Savo sub-region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubregionRole Context triple: [Iisalmi, hasSubregionRole, center of Upper Savo sub-region]
-
A.
hasSubregionRelationWith
Indicates a relationship where one region is a subregion or contained part of another region.
-
B.
hasSubregionStatus
Indicates that one region holds an official or defined status as a subregion within a larger geographic or administrative area.
-
C.
isInSubregion
Indicates that one region or area is located within the boundaries of another, more specific subregion.
-
D.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
E.
originSubregion
Indicates the specific subregional area from which an entity originates or is derived.
- F. None of above. chosen
Provenance (4 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a007ef69f5c8190be6fb89e918d30fa |
completed | May 10, 2026, 12:49 p.m. |
| PD | Predicate disambiguation | batch_6a007e4060448190ad7420b07c1fe219 |
completed | May 10, 2026, 12:46 p.m. |
| PDg | Predicate description generation | batch_6a007ef5f05c8190a2d43e4bc45fba3f |
completed | May 10, 2026, 12:49 p.m. |
Created at: May 3, 2026, 4:30 p.m.