Triple

T5832955
Position Surface form Disambiguated ID Type / Status
Subject Bockenheim E129394 entity
Predicate hasNeighbourhood P4813 FINISHED
Object Hausen E483358 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: Hausen | Statement: [Bockenheim, hasNeighbourhood, Hausen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hausen
Context triple: [Bockenheim, hasNeighbourhood, Hausen]
  • A. Hausen chosen
    Hausen is a small suburban district of the town of Herbrechtingen in the state of Baden-Württemberg, Germany.
  • B. Wienhausen
    Wienhausen is a historic village in Lower Saxony, Germany, best known for its medieval Cistercian nunnery and well-preserved half-timbered architecture.
  • C. Hausen an der Würm
    Hausen an der Würm is a village and district of the town Weil der Stadt in the German state of Baden-Württemberg.
  • D. Fleinhausen
    Fleinhausen is a small village in Bavaria, Germany, historically noted as the birthplace of Nazi propagandist Julius Streicher.
  • E. Alfhausen
    Alfhausen is a small municipality in Lower Saxony, Germany, known for its rural character and location within the Osnabrück 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_69c0084af79c81908af128ccc29983d0 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0346e6e9c8190a245e5d10595a68f completed March 22, 2026, 6:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0a193ac408190a06159406a814adb completed March 23, 2026, 2:12 a.m.
Created at: March 22, 2026, 3:54 p.m.