Triple
T12914984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mykland Church |
E308956
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Mykland |
E308950
|
NE 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: Mykland | Statement: [Mykland Church, locatedIn, Mykland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mykland Context triple: [Mykland Church, locatedIn, Mykland]
-
A.
Mykland
chosen
Mykland is a small village in Agder county, Norway, known for its rural setting and surrounding forests and lakes.
-
B.
Helleland
Helleland is a small village in Rogaland county, Norway, situated within the municipality of Eigersund.
-
C.
Vestland
Vestland is a county in western Norway known for its dramatic fjords, coastal landscapes, and the city of Bergen.
-
D.
Forlandet
Forlandet is a long, narrow island off the west coast of Spitsbergen in the Svalbard archipelago, known for its protected wilderness and rich Arctic wildlife.
-
E.
Skåneland
Skåneland is a historical region in southern Scandinavia encompassing the provinces around present-day Skåne, known for its shifting rule between Denmark and Sweden and its central role in medieval Nordic history.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971a0d6508190bca9668e9e06abfe |
completed | April 10, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a571a3e48190a32d362adc6eaee2 |
completed | May 3, 2026, 1:31 a.m. |
Created at: April 9, 2026, 5:41 p.m.