Triple
T8591982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyhäranta |
E203448
|
entity |
| Predicate | hasMunicipalManager |
P16141
|
FINISHED |
| Object | municipal manager of Pyhäranta |
—
|
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: municipal manager of Pyhäranta | Statement: [Pyhäranta, hasMunicipalManager, municipal manager of Pyhäranta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalManager Context triple: [Pyhäranta, hasMunicipalManager, municipal manager of Pyhäranta]
-
A.
hasCityManager
chosen
Indicates that an entity has a specific individual who serves in the role of city manager for it.
-
B.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
C.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
D.
hasMayor
Indicates that one entity serves as the mayor of another entity, typically a city, town, or 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.