Triple

T15021790
Position Surface form Disambiguated ID Type / Status
Subject Stetinden E378101 entity
Predicate near P350 FINISHED
Object Tysfjorden E439360 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: Tysfjorden | Statement: [Stetinden, near, Tysfjorden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tysfjorden
Context triple: [Stetinden, near, Tysfjorden]
  • A. Tysfjorden chosen
    Tysfjorden is a dramatic fjord in Nordland county, northern Norway, known for its steep mountains, deep waters, and scenic Arctic landscapes.
  • B. Strindfjorden
    Strindfjorden is a bay-like arm of the Trondheimsfjord in central Norway, known for bordering parts of the city of Trondheim and its surrounding coastal landscape.
  • C. Namsenfjorden
    Namsenfjorden is a fjord in Trøndelag county, Norway, known for its scenic coastal landscape and connection to the Namsen River near the town of Namsos.
  • D. 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.
  • E. Dalsfjorden
    Dalsfjorden is a fjord in western Norway known for its steep surrounding mountains, deep waters, and small coastal settlements.
  • 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_69d85cd3a3c881908c71fc424d459c17 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded765462c819097f331c9b39c80e3 completed April 15, 2026, 12:10 a.m.
NED1 Entity disambiguation (via context triple) batch_6a007d960bd08190b8ac366273646865 completed May 10, 2026, 12:44 p.m.
Created at: April 10, 2026, 2:56 a.m.