Triple

T12887130
Position Surface form Disambiguated ID Type / Status
Subject Darmstadt-Dieburg E308256 entity
Predicate contains P35 FINISHED
Object Erzhausen E23310 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: Erzhausen | Statement: [Darmstadt-Dieburg, contains, Erzhausen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Erzhausen
Context triple: [Darmstadt-Dieburg, contains, Erzhausen]
  • A. Erzhausen chosen
    Erzhausen is a small municipality in the state of Hesse in central Germany, located near Darmstadt and part of the Rhine-Main metropolitan region.
  • B. Hohen Viecheln
    Hohen Viecheln is a small municipality in the Mecklenburg-Vorpommern region of northern Germany, situated on the shores of Lake Schwerin.
  • C. Hohenthann
    Hohenthann is a rural municipality in Lower Bavaria, Germany, known for its agricultural character and location within the Landshut district.
  • D. Eibenberg
    Eibenberg is a small locality that forms one of the subdivisions of the municipality of Burkhardtsdorf in Saxony, Germany.
  • E. Sendenhorst
    Sendenhorst is a small town in the German state of North Rhine-Westphalia, known for its rural character and location in the Münsterland region.
  • 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_69d7bdf7c1f0819098102569a8d8cbf5 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9714415c08190aa9944b494a3ddad completed April 10, 2026, 9:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6af57a8b88190a3f15a3e9e02d492 completed May 3, 2026, 2:13 a.m.
Created at: April 9, 2026, 5:39 p.m.