Triple

T9080368
Position Surface form Disambiguated ID Type / Status
Subject Vechta E217603 entity
Predicate locatedNear P294 FINISHED
Object Oldenburg E73235 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: Oldenburg | Statement: [Vechta, locatedNear, Oldenburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oldenburg
Context triple: [Vechta, locatedNear, Oldenburg]
  • A. Oldenburg chosen
    Oldenburg is a historic university city in northwestern Germany known for its cultural heritage and role as a regional economic center.
  • B. Oldenburg
    Oldenburg is a historic European noble house that ruled various territories in Denmark, Norway, and northern Germany and provided numerous monarchs to several European thrones.
  • C. Flensburg
    Flensburg is a historic port city in northern Germany near the Danish border, known for its maritime heritage and role as a regional administrative and cultural center in Schleswig-Holstein.
  • D. Itzehoe
    Itzehoe is a historic town in northern Germany known for its medieval origins and role as a regional center in the state of Schleswig-Holstein.
  • E. Wallhausen
    Wallhausen is a village in present-day Saxony-Anhalt, Germany, historically notable as the birthplace of Otto I, Holy Roman Emperor.
  • 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_69ca83d7a0388190ba1af89ed7ba36f9 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc9607942c8190a21620892ce3cbe5 completed April 1, 2026, 3:50 a.m.
NED1 Entity disambiguation (via context triple) batch_69cffe28ae548190924cc7bbf453f3f3 completed April 3, 2026, 5:51 p.m.
Created at: March 30, 2026, 7:13 p.m.