Triple

T6426023
Position Surface form Disambiguated ID Type / Status
Subject Trondheimsfjord E128059 entity
Predicate hasInlet P23365 FINISHED
Object Beitstadfjorden E558831 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: Beitstadfjorden | Statement: [Trondheimsfjord, hasInlet, Beitstadfjorden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beitstadfjorden
Context triple: [Trondheimsfjord, hasInlet, Beitstadfjorden]
  • A. Beitstadfjorden chosen
    Beitstadfjorden is an inner branch of the Trondheimsfjord in Trøndelag county, Norway, known for its sheltered waters and surrounding agricultural and forested landscapes.
  • B. Beisfjorden
    Beisfjorden is a fjord in Nordland county, Norway, known as an inner branch of the larger Ofotfjord near the town of Narvik.
  • C. Bjørnafjorden
    Bjørnafjorden is a large fjord in western Norway known for its scenic coastal landscape and role as an important marine and transport corridor in Vestland county.
  • D. Bremnesfjorden
    Bremnesfjorden is a fjord in Norway known for its coastal landscape along the island of Averøya.
  • E. Randsfjorden
    Randsfjorden is one of Norway’s largest inland lakes, located in Eastern Norway and known for its elongated shape and surrounding forested landscapes.
  • 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_69c00838de888190af2eec0b80495efa completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0691f944c81909d4e5d8ef9e494b6 completed March 22, 2026, 10:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69c67c3f115481909879d637fc231556 completed March 27, 2026, 12:46 p.m.
Created at: March 22, 2026, 4:43 p.m.