Triple

T13355381
Position Surface form Disambiguated ID Type / Status
Subject Lech riverfront E318677 entity
Predicate viewOf P854 FINISHED
Object River Lech E854009 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: River Lech | Statement: [Lech riverfront, viewOf, River Lech]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Lech
Context triple: [Lech riverfront, viewOf, River Lech]
  • A. river Lech chosen
    The river Lech is a major Alpine river flowing through Austria and Germany, known for its fast currents, striking gorges, and role as a significant tributary of the Danube.
  • B. Orlice River
    The Orlice River is a significant river in the Czech Republic that flows through eastern Bohemia and joins the Elbe near the city of Hradec Králové.
  • C. Saalach River
    The Saalach River is an Alpine river in Austria and Germany that flows through the spa town of Bad Reichenhall before joining the Salzach.
  • D. Lech River
    The Lech River is a major Alpine river flowing through Austria and southern Germany, known for its scenic course, hydropower use, and role as a tributary of the Danube.
  • E. Örtze River
    The Örtze River is a river in Lower Saxony, Germany, known for flowing through the Lüneburg Heath before joining the Aller.
  • 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_69d806b7bbac8190b85278c87fa7aff3 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99f1ef94c81909a59b7c3f77d3335 completed April 11, 2026, 1:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69fd46686c288190a51847f86785568a completed May 8, 2026, 2:11 a.m.
Created at: April 9, 2026, 9:32 p.m.