Triple

T1739505
Position Surface form Disambiguated ID Type / Status
Subject Leipzig E38199 entity
Predicate locatedOn P40 FINISHED
Object Pleisse River E255735 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: Pleisse River | Statement: [Leipzig, locatedOn, Pleisse River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pleisse River
Context triple: [Leipzig, locatedOn, Pleisse River]
  • A. River Pleiße chosen
    The River Pleiße is a small river in central Germany that flows through the city and district of Leipzig, contributing to the region’s historic waterways and green corridors.
  • B. Inn River
    The Inn River is a major Alpine river in Central Europe that flows through Switzerland, Austria, and Germany before joining the Danube.
  • C. Blau River
    The Blau River is a small river in the state of Baden-Württemberg in southern Germany, known for flowing through the Swabian Jura and joining the Danube at Ulm.
  • D. Chemnitz River
    The Chemnitz River is a waterway in the German state of Saxony that flows through and gives its name to the city of Chemnitz.
  • E. Wertach River
    The Wertach River is a tributary waterway in Bavaria, Germany, flowing northward through towns such as Kaufbeuren and Augsburg before joining the Lech River.
  • 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_69a8862b01a48190ab47209063af82d9 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa63c4639c81908b91b2559f0c6a5c completed March 6, 2026, 5:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69aebefcac108190a60448f545c89a26 completed March 9, 2026, 12:37 p.m.
Created at: March 4, 2026, 7:30 p.m.