Triple

T21311528
Position Surface form Disambiguated ID Type / Status
Subject Deurne E525348 entity
Predicate hasLandmark P105 FINISHED
Object Rivierenhof 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: Rivierenhof | Statement: [Deurne, hasLandmark, Rivierenhof]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rivierenhof
Context triple: [Deurne, hasLandmark, Rivierenhof]
  • A. Rivierenhof chosen
    Rivierenhof is a large public park in the Deurne district of Antwerp, Belgium, known for its extensive greenery, ponds, and recreational facilities.
  • B. Schlungenhof
    Schlungenhof is a small settlement in Bavaria, Germany, situated close to the recreational Altmühlsee lake.
  • C. Grabenhof
    Grabenhof is a notable building complex located on Vienna’s historic Graben street, known for its characteristic 19th-century architecture and prominent city-center location.
  • D. Gleimhaus
    Gleimhaus is a literary museum in Halberstadt, Germany, dedicated to the life, work, and extensive correspondence of 18th-century poet and collector Johann Wilhelm Ludwig Gleim.
  • E. Sippenaeken
    Sippenaeken is a small village in eastern Belgium, near the Dutch and German borders, known for its rural landscape and historic church.
  • 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_69e0b518b8948190ad69cf9a8784d397 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e75dc926c881909d70a317070ef295 completed April 21, 2026, 11:21 a.m.
Created at: April 16, 2026, 4:17 p.m.