Triple

T6426010
Position Surface form Disambiguated ID Type / Status
Subject Trondheimsfjord E128059 entity
Predicate hasCityOnShore P969 FINISHED
Object Trondheim E136993 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: Trondheim | Statement: [Trondheimsfjord, hasCityOnShore, Trondheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Trondheim
Context triple: [Trondheimsfjord, hasCityOnShore, Trondheim]
  • A. Trondheim chosen
    Trondheim is a historic Norwegian city in Trøndelag county, known for its medieval Nidaros Cathedral and role as a former capital of Norway.
  • B. Oslo
    Oslo is the capital and largest city of Norway, known as a major cultural, economic, and governmental center.
  • C. Bergen
    Bergen is Norway's second-largest city, renowned for its historic harbor, surrounding mountains and fjords, and role as a former Hanseatic trading hub.
  • D. Bergen
    Bergen is a city in western Germany, historically notable as the site of the 1759 Battle of Bergen during the Seven Years' War.
  • E. Bergens
    The Bergens are a race of gloomy, troll-eating creatures who serve as the primary villains in the animated film "Trolls."
  • 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_69c7eeb127248190bbee7a9f69c2b980 completed March 28, 2026, 3:07 p.m.
Created at: March 22, 2026, 4:43 p.m.