Triple
T15333685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hordaland |
E366605
|
entity |
| Predicate | containsTown |
P847
|
FINISHED |
| Object | Leirvik |
E371041
|
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: Leirvik | Statement: [Hordaland, containsTown, Leirvik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leirvik Context triple: [Hordaland, containsTown, Leirvik]
-
A.
Leirvik
chosen
Leirvik is the main town on the island of Stord in western Norway, serving as an important local commercial and administrative center.
-
B.
Lugnvik
Lugnvik is a residential area and locality within Östersund Municipality in central Sweden, known for its proximity to Lake Storsjön and the city of Östersund.
-
C.
Hoddevik
Hoddevik is a small coastal village in western Norway known for its scenic bay, sandy beach, and popularity as a surfing destination.
-
D.
Ulsteinvik
Ulsteinvik is a coastal town in western Norway known for its maritime industry and shipbuilding, serving as the administrative center of Ulstein Municipality.
-
E.
Birketveit
Birketveit is a village in Agder county, Norway, serving as the main local hub for municipal services and community life in Iveland.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e0268608190947a58f559a67717 |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4c2efb148190a2e6c0811f2afb5f |
completed | May 9, 2026, 3:01 p.m. |
Created at: April 10, 2026, 3:17 a.m.