Triple
T15529034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strand |
E370161
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Sandnes (across fjord) |
E1051193
|
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: Sandnes (across fjord) | Statement: [Strand, borders, Sandnes (across fjord)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sandnes (across fjord) Context triple: [Strand, borders, Sandnes (across fjord)]
-
A.
Sandnes (Bygland)
chosen
Sandnes (Bygland) is a small village in Bygland municipality in Agder county, southern Norway, situated in the Setesdal valley.
-
B.
Fosnes
Fosnes was a former rural municipality in Trøndelag county, Norway, known for its coastal landscape and small, dispersed population.
-
C.
Sandnes
Sandnes is a city in southwestern Norway, near Stavanger, known for its proximity to fjords and outdoor recreation areas.
-
D.
Skudeneshavn
Skudeneshavn is a historic coastal town in southwestern Norway known for its well-preserved wooden architecture and maritime heritage.
-
E.
Bremsnes
Bremsnes is a village on the island of Averøya in Møre og Romsdal county, Norway, known for its coastal setting and local church.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414620588190958ffde651ccab5f |
completed | April 16, 2026, 1:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3d5b989c8190a76612df167ba1dd |
completed | May 9, 2026, 1:57 p.m. |
Created at: April 10, 2026, 4:05 a.m.