Triple

T12420656
Position Surface form Disambiguated ID Type / Status
Subject Altenburg E296758 entity
Predicate hasRiver P165 FINISHED
Object Pleiße E889203 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: Pleiße | Statement: [Altenburg, hasRiver, Pleiße]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pleiße
Context triple: [Altenburg, hasRiver, Pleiße]
  • A. Pleiße chosen
    Pleiße is a river in eastern Germany that flows through the city of Leipzig and is a tributary of the White Elster.
  • B. Seebruck
    Seebruck is a Bavarian lakeside village and popular holiday resort on the northern shore of Lake Chiemsee in southern Germany.
  • C. Wielenbach
    Wielenbach is a small municipality in the Upper Bavarian region of Germany, situated within the district of Weilheim-Schongau.
  • D. Seebach
    Seebach is a quarter in the northern part of Zurich, Switzerland, known for its residential areas and proximity to major transport links.
  • E. Horgau
    Horgau is a small municipality in the Swabian region of Bavaria in southern Germany.
  • 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_69d6ada0640c81908c061d7fb3d47786 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d6efd748190a5d9396a343e41e1 completed April 10, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f63f0265fc81909a6288d11b78c2f9 completed May 2, 2026, 6:14 p.m.
Created at: April 8, 2026, 9:55 p.m.