Triple
T1014417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haninge Municipality |
E21897
|
entity |
| Predicate | municipalCode |
P3943
|
FINISHED |
| Object | 0136 |
—
|
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: 0136 | Statement: [Haninge Municipality, municipalCode, 0136]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalCode Context triple: [Haninge Municipality, municipalCode, 0136]
-
A.
hasMunicipalityCode
chosen
Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
-
B.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
-
C.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
D.
isInMunicipality
Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
-
E.
specialMunicipality
Indicates that an entity is designated as a special municipality, typically having a distinct administrative or legal status compared to regular municipalities.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7be907c8190b5c6ea89257755a7 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b72207c08190a3dbb2aa7acbbc71 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.