Triple

T3701388
Position Surface form Disambiguated ID Type / Status
Subject Sotra E78585 entity
Predicate locatedInBodyOfWater P1714 FINISHED
Object Byfjorden E363649 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: Byfjorden | Statement: [Sotra, locatedInBodyOfWater, Byfjorden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Byfjorden
Context triple: [Sotra, locatedInBodyOfWater, Byfjorden]
  • A. Byfjorden chosen
    Byfjorden is a coastal fjord in western Norway that forms the main seaway and natural harbor area adjacent to the city of Bergen.
  • 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. Storfjorden
    Storfjorden is a major fjord in western Norway known for its dramatic landscapes and proximity to the coastal town of Ålesund.
  • E. Bremnesfjorden
    Bremnesfjorden is a fjord in Norway known for its coastal landscape along the island of Averøya.
  • 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_69ad85e3b1888190abc983e06968696d completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc547c1848190a1ece46c59b7c43d completed March 8, 2026, 6:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69bb60d49ba08190b954fedd4c7bef5f completed March 19, 2026, 2:35 a.m.
Created at: March 8, 2026, 3:26 p.m.