Triple

T23005927
Position Surface form Disambiguated ID Type / Status
Subject Made E572766 entity
Predicate hasNeighbouringSettlement P4647 FINISHED
Object Wagenberg NE NERFINISHED

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: Wagenberg | Statement: [Made, hasNeighbouringSettlement, Wagenberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wagenberg
Context triple: [Made, hasNeighbouringSettlement, Wagenberg]
  • A. Wagenberg chosen
    Wagenberg is a village in the Dutch province of North Brabant, located within the municipality of Drimmelen.
  • B. Stenzelberg
    Stenzelberg is a prominent hill of volcanic origin in Germany’s Siebengebirge range, known for its distinctive rocky summit and surrounding nature reserve.
  • C. Patersberg
    Patersberg is a small village in western Germany’s Upper Middle Rhine Valley, known for its scenic location overlooking the Rhine near the famous Loreley Rock.
  • D. Wilseder Berg
    Wilseder Berg is a prominent hill and popular viewpoint in northern Germany, known for its scenic heathland landscapes within the Lüneburg Heath region.
  • E. Gamsberg
    Gamsberg is a prominent mountain in Namibia known for its flat-topped summit and exceptionally clear skies that make it a favored site for astronomical observations.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245b6a3ac81908087599eefe3e365 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18356417881908c8d6ee56bdc85f5 completed April 29, 2026, 4:04 a.m.
Created at: April 17, 2026, 3:51 p.m.