Triple

T15344057
Position Surface form Disambiguated ID Type / Status
Subject Aurlandsfjord E366869 entity
Predicate isPartOf P10 FINISHED
Object Sognefjord system E74083 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: Sognefjord system | Statement: [Aurlandsfjord, isPartOf, Sognefjord system]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sognefjord system
Context triple: [Aurlandsfjord, isPartOf, Sognefjord system]
  • A. Sognefjord chosen
    Sognefjord is Norway’s longest and deepest fjord, renowned for its dramatic cliffs, glacial landscapes, and scenic coastal villages.
  • B. Osafjorden
    Osafjorden is a side fjord of Norway’s Hardangerfjord, known for its steep mountain scenery and tranquil, narrow waters.
  • C. Trondheimsfjord
    Trondheimsfjord is a major Norwegian fjord on the central coast, known for its deep waters, rich marine life, and the city of Trondheim along its shores.
  • D. Sifjord
    Sifjord is a small coastal village in northern Norway, situated on the island of Senja within Troms og Finnmark county.
  • E. Isfjorden
    Isfjorden is a major Arctic fjord on the west coast of Spitsbergen in the Svalbard archipelago, known for its dramatic glacial landscapes and as a key hub for human settlement and wildlife.
  • 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_69d85a1355608190a6673ddb67231d54 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e163a3c8190ab933411372c1573 completed April 16, 2026, 1:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff01f70e688190bb6a073e49ff968c completed May 9, 2026, 9:44 a.m.
Created at: April 10, 2026, 3:17 a.m.