Triple

T997025
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Ryswick E21517 entity
Predicate tookPlaceAt P373 FINISHED
Object Rijswijk E116357 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: Rijswijk | Statement: [Treaty of Ryswick, tookPlaceAt, Rijswijk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rijswijk
Context triple: [Treaty of Ryswick, tookPlaceAt, Rijswijk]
  • A. Rijswijk chosen
    Rijswijk is a town in the western Netherlands, near The Hague, historically notable as the site where the 1697 Treaty of Rijswijk ended the Nine Years' War.
  • B. Haarlem
    Haarlem is a historic Dutch city in the province of North Holland, known for its medieval architecture, cultural heritage, and role as a regional center near Amsterdam.
  • C. Barendrecht
    Barendrecht is a suburban town in the western Netherlands, located just south of Rotterdam and known for its residential character and logistics industry.
  • D. Apeldoorn
    Apeldoorn is a city in the province of Gelderland in the Netherlands, known for the royal palace Het Loo and its historical ties to the Dutch monarchy.
  • E. Zoetermeer
    Zoetermeer is a modern, rapidly grown satellite city of The Hague in the western Netherlands, known for its residential neighborhoods and light-rail connections.
  • 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_69a493c476b48190b41fc5e793171cc6 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b4e0f0d081908b888c246d001786 completed March 1, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69bd566575a88190a03a306fbe40f8c9 completed March 20, 2026, 2:15 p.m.
Created at: March 1, 2026, 7:41 p.m.