Triple
T13147411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torsken |
E312374
|
entity |
| Predicate | wasMunicipalityUntil |
P5557
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Torsken, wasMunicipalityUntil, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMunicipalityUntil Context triple: [Torsken, wasMunicipalityUntil, 2020]
-
A.
partOfMunicipalitySince
Indicates that an entity has been included within and administratively belonging to a specific municipality starting from a given point in time.
-
B.
formerMunicipalityOf
chosen
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
C.
existedAsCountyUntil
Indicates that an entity functioned with the status or designation of a county up to a specified end date or time period.
-
D.
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.
-
E.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:10 p.m.