Triple

T6487786
Position Surface form Disambiguated ID Type / Status
Subject Beuel E146557 entity
Predicate hasPart P35 FINISHED
Object Beuel-Ost E146557 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: Beuel-Ost | Statement: [Beuel, hasPart, Beuel-Ost]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beuel-Ost
Context triple: [Beuel, hasPart, Beuel-Ost]
  • A. Beuel chosen
    Beuel is a district on the right bank of the Rhine in the German city of Bonn, known for its residential areas and local carnival traditions.
  • B. Bernlohe
    Bernlohe is a village-level district that forms part of the town of Roth in Bavaria, Germany.
  • C. Bielkenfeld
    Bielkenfeld is a locality in the historical region of Prussia, known as the birthplace of the German field marshal and military writer Colmar Freiherr von der Goltz.
  • D. Ochsenfeld
    Ochsenfeld is a German surname most notably borne by physicist Robert Ochsenfeld, known for his work on superconductivity.
  • E. Neudorf
    Neudorf is a residential district of Strasbourg, France, known for its dense urban fabric, local commerce, and proximity to the city 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_69c0090158c08190af0df9a2348d2d52 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06a96a4048190a28dee5fd9258486 completed March 22, 2026, 10:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c653b792f48190b301cdc643db8ddf completed March 27, 2026, 9:53 a.m.
Created at: March 22, 2026, 4:52 p.m.