Triple

T21814115
Position Surface form Disambiguated ID Type / Status
Subject Kungsängsbron E538553 entity
Predicate crosses P416 FINISHED
Object Fyris River NE NERFINISHED

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: Fyris River | Statement: [Kungsängsbron, crosses, Fyris River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fyris River
Context triple: [Kungsängsbron, crosses, Fyris River]
  • A. Fyris River chosen
    The Fyris River is a notable waterway in eastern Sweden that flows through the city of Uppsala and is closely associated with its history and landscape.
  • B. Lærdalselvi
    Lærdalselvi is a renowned salmon river in western Norway, flowing through the Lærdal valley to the Sognefjord and known for both its fishing and scenic landscape.
  • C. Österdal River
    The Österdal River is a major river in central Sweden that flows through the Dalarna region and joins the Västerdal River to form the Dalälven.
  • D. Eidselva
    Eidselva is a river in Norway that serves as one of the main waterways feeding into the lake Norsjø.
  • E. Arve River
    The Arve River is a glacial river in the Alps that flows through France and Switzerland, notably passing through Geneva before joining the Rhône.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c473f0f8819086c9d1b4a143bd67 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f07cc8e6808190bde4d0e0981e4117 completed April 28, 2026, 9:24 a.m.
Created at: April 16, 2026, 6:54 p.m.