Triple

T22962405
Position Surface form Disambiguated ID Type / Status
Subject Gamle Bybro E570936 entity
Predicate crosses P416 FINISHED
Object Nidelva E567375 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: Nidelva | Statement: [Gamle Bybro, crosses, Nidelva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nidelva
Context triple: [Gamle Bybro, crosses, Nidelva]
  • A. Nidelva chosen
    Nidelva is the main river flowing through Trondheim, Norway, known for its scenic bends, historic waterfront buildings, and central role in the city’s landscape.
  • B. Nidelva river
    Nidelva river is a river in southern Norway that flows through the county of Agder, including the municipality of Froland, before reaching the city of Arendal and the Skagerrak coast.
  • C. Hunnselva
    Hunnselva is a river in Innlandet county, Norway, flowing through the town of Raufoss and contributing to the local industrial and natural landscape.
  • D. Solbergelva
    Solbergelva is a village in Viken county, Norway, situated along the Drammenselva river and functioning largely as a residential suburb of Drammen.
  • E. Fykseelva
    Fykseelva is a river flowing through the municipality of Kvam in Vestland county, western Norway, known for its scenic valley and salmon fishing.
  • 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_69e245b212a88190b5259caf51606084 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f181f594fc8190816418486b798198 completed April 29, 2026, 3:58 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0c5daa149c8190aa95908bd6dd8767 completed May 19, 2026, 12:55 p.m.
Created at: April 17, 2026, 3:47 p.m.