Triple

T7313062
Position Surface form Disambiguated ID Type / Status
Subject Helene Weber E168141 entity
Predicate placeOfBirth P1 FINISHED
Object Wuppertal E173299 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: Wuppertal | Statement: [Helene Weber, placeOfBirth, Wuppertal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wuppertal
Context triple: [Helene Weber, placeOfBirth, Wuppertal]
  • A. Wuppertal chosen
    Wuppertal is a city in western Germany known for its steep slopes, extensive parks, and the unique suspended monorail Wuppertal Schwebebahn.
  • B. Duisburg
    Duisburg is a major industrial and port city in western Germany’s Ruhr region, known for its steel production and one of the world’s largest inland harbors.
  • C. Cologne
    Cologne is a historic German city on the Rhine River, renowned for its Gothic cathedral, vibrant cultural scene, and status as a major economic and media hub.
  • D. Krefeld
    Krefeld is a city in western Germany near the Rhine River, known historically for its textile and silk industry.
  • E. Mülheim an der Ruhr
    Mülheim an der Ruhr is a city in western Germany’s Ruhr area, known for its industrial heritage, riverside setting on the Ruhr River, and role as a regional economic and cultural center.
  • 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_69c6888d8e3c81909db79714903baf31 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6ec02319c819096d25e3683943886 completed March 27, 2026, 8:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69ccbd5d671481908ecbdb8ce6ef898a completed April 1, 2026, 6:38 a.m.
Created at: March 27, 2026, 3:02 p.m.