Triple
T16045809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnås |
E389214
|
entity |
| Predicate | locatedInMunicipalityType |
P108590
|
FINISHED |
| Object | island 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: island municipality | Statement: [Finnås, locatedInMunicipalityType, island municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMunicipalityType Context triple: [Finnås, locatedInMunicipalityType, island municipality]
-
A.
isInMunicipality
Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
-
B.
isPartOfMunicipalityType
chosen
Indicates that one administrative unit or area belongs to, or is classified under, a specific type or category of municipality.
-
C.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
D.
hasMunicipalityType
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
-
E.
locatedInPresentDayMunicipality
Indicates that an entity is situated within the boundaries of a specific municipality as it exists in the present day, regardless of historical administrative changes.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.