Triple
T15529046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strand |
E370161
|
entity |
| Predicate | hasFjord |
P56784
|
FINISHED |
| Object | Høgsfjorden (shoreline) |
E1131424
|
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: Høgsfjorden (shoreline) | Statement: [Strand, hasFjord, Høgsfjorden (shoreline)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Høgsfjorden (shoreline) Context triple: [Strand, hasFjord, Høgsfjorden (shoreline)]
-
A.
Aurlandsfjord shoreline
Aurlandsfjord shoreline is the scenic waterfront along Norway’s Aurlandsfjord, known for its dramatic fjord landscapes, steep mountainsides, and picturesque villages.
-
B.
Høgsfjorden
chosen
Høgsfjorden is a fjord in Rogaland county in southwestern Norway, known for its deep waters and scenic landscapes near the city of Stavanger.
-
C.
Horgefjorden
Horgefjorden is a fjord in Rogaland county, Norway, known for its coastal landscapes and proximity to the island municipality of Finnøy.
-
D.
Hylsfjorden
Hylsfjorden is a narrow, scenic fjord in Rogaland county in southwestern Norway, known as part of the Ryfylke fjord system.
-
E.
Topdalsfjorden
Topdalsfjorden is a coastal fjord in southern Norway, located near the city of Kristiansand in Agder county.
- 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.