Triple
T16027264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vågsøy |
E388746
|
entity |
| Predicate | wasMunicipalityFrom |
P118208
|
FINISHED |
| Object | 1964 |
—
|
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: 1964 | Statement: [Vågsøy, wasMunicipalityFrom, 1964]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMunicipalityFrom Context triple: [Vågsøy, wasMunicipalityFrom, 1964]
-
A.
wasMunicipalityIn
Indicates that an entity previously held the status of a municipality within a specified administrative or territorial unit.
-
B.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
C.
wasMunicipiumUnder
Indicates that a settlement or city held the legal status of a municipium under the authority or jurisdiction of a specified ruling power or polity.
-
D.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
E.
formedMunicipalityOn
chosen
Indicates that a new municipality was officially created or established on a specific date.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.