Triple

T3790657
Position Surface form Disambiguated ID Type / Status
Subject Oldenburg–Osnabrück region E89637 entity
Predicate containsCity 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: [Oldenburg–Osnabrück region, containsCity, Oldenburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oldenburg
Context triple: [Oldenburg–Osnabrück region, containsCity, 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. 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.
  • C. Wallhausen
    Wallhausen is a village in present-day Saxony-Anhalt, Germany, historically notable as the birthplace of Otto I, Holy Roman Emperor.
  • D. Bremerhaven
    Bremerhaven is a major German port city on the North Sea, known for its maritime industry, shipbuilding, and role as a key hub for trade and logistics.
  • E. Soest
    Soest is a historic town in North Rhine-Westphalia, Germany, known for its well-preserved medieval architecture and former significance as a Hanseatic trading 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_69aed9597d6881909b6ee3b9de859223 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aee76733248190a24a1143c64bd6c6 completed March 9, 2026, 3:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4fb1f7a20819082d2ff104167d98b completed March 14, 2026, 6:07 a.m.
Created at: March 9, 2026, 3:15 p.m.