Triple

T15575099
Position Surface form Disambiguated ID Type / Status
Subject Aurland E374347 entity
Predicate contains P35 FINISHED
Object Aurlandsfjord E366869 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: Aurlandsfjord | Statement: [Aurland, contains, Aurlandsfjord]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aurlandsfjord
Context triple: [Aurland, contains, Aurlandsfjord]
  • A. Aurlandsfjord chosen
    Aurlandsfjord is a scenic branch of Norway’s Sognefjord, renowned for its steep mountainsides, deep blue waters, and picturesque fjord villages.
  • B. Finnfjorden
    Finnfjorden is a Norwegian fjord located in Troms og Finnmark county, known for its rugged coastal scenery and connection to surrounding straits and waterways.
  • C. Vartdalsfjorden
    Vartdalsfjorden is a fjord in the Sunnmøre region of Møre og Romsdal county in western Norway, known for its steep surrounding mountains and coastal landscapes.
  • D. Hjørundfjord
    Hjørundfjord is a dramatic, narrow fjord in Norway’s Sunnmøre region, renowned for its steep mountain walls, deep waters, and scenic, relatively untouched natural landscapes.
  • E. Osafjorden
    Osafjorden is a side fjord of Norway’s Hardangerfjord, known for its steep mountain scenery and tranquil, narrow waters.
  • 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_69d85ccd575081908909b71a3f3e3a61 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e2140388190a8df7b835eaa72ce completed April 16, 2026, 2:49 a.m.
NED1 Entity disambiguation (via context triple) batch_6a091fab0bf08190a851081f762bab68 completed May 17, 2026, 1:53 a.m.
Created at: April 10, 2026, 4:10 a.m.