Triple
T23543719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köpingsvik Church |
E577828
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Köpingsvik |
—
|
NE NERFINISHED |
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: Köpingsvik | Statement: [Köpingsvik Church, locatedIn, Köpingsvik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Köpingsvik Context triple: [Köpingsvik Church, locatedIn, Köpingsvik]
-
A.
Köpingsvik
chosen
Köpingsvik is a coastal village and popular holiday resort on the Swedish island of Öland, known for its sandy beaches and historic church.
-
B.
Drotningsvik
Drotningsvik is a coastal neighborhood in the western part of Bergen, Norway, situated along the main route connecting the city to the island of Sotra.
-
C.
Kirkelandet
Kirkelandet is the central island and main urban area of the Norwegian coastal city of Kristiansund.
-
D.
Bråviken Bay
Bråviken Bay is a long, narrow inlet of the Baltic Sea in eastern Sweden, known for its scenic coastline and proximity to the city of Norrköping.
-
E.
Tømmervik
Tømmervik is a small settlement located within the municipality of Sørreisa in Troms og Finnmark county, northern Norway.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1dbe188190bc4afe7bfa7cda0f |
completed | April 29, 2026, 7:07 a.m. |
Created at: April 17, 2026, 6:11 p.m.