Triple

T7548848
Position Surface form Disambiguated ID Type / Status
Subject Weinheim E178475 entity
Predicate locatedAtRiver P17819 FINISHED
Object Weschnitz E425989 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: Weschnitz | Statement: [Weinheim, locatedAtRiver, Weschnitz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Weschnitz
Context triple: [Weinheim, locatedAtRiver, Weschnitz]
  • A. Weschnitz chosen
    Weschnitz is a river in southwestern Germany that flows from the Odenwald hills through Hesse and Baden-Württemberg before joining the Rhine.
  • B. Würschnitz
    Würschnitz is a small river in Saxony, Germany, that serves as one of the tributaries feeding into the Chemnitz River.
  • C. Schwabach
    Schwabach is a historic town in northern Bavaria, Germany, known for its traditional gold-beating craft and well-preserved old town.
  • D. Orlice
    Orlice is a river in the Czech Republic that flows through the city of Hradec Králové and is a tributary of the Labe (Elbe) River.
  • E. River Wörnitz
    River Wörnitz is a river in Bavaria, Germany, that flows through historic towns such as Dinkelsbühl before joining the Danube.
  • 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_69c69f2cbe08819088f9eb0c03ef529b completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f89b9afc8190b3e61a8e2cea7ad7 completed March 27, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69c84f2b0de48190a854b4d4935c2254 completed March 28, 2026, 9:59 p.m.
Created at: March 27, 2026, 3:49 p.m.