Triple

T1218722
Position Surface form Disambiguated ID Type / Status
Subject Oude Maas E26167 entity
Predicate locatedNear P294 FINISHED
Object Spijkenisse E70497 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: Spijkenisse | Statement: [Oude Maas, locatedNear, Spijkenisse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Spijkenisse
Context triple: [Oude Maas, locatedNear, Spijkenisse]
  • A. Spijkenisse chosen
    Spijkenisse is a town and former municipality in the western Netherlands, now part of the municipality of Nissewaard and known as a suburban area near Rotterdam.
  • B. Veermansplaat
    Veermansplaat is a small, uninhabited island and nature area located in the Grevelingen estuary in the southwestern Netherlands.
  • C. Herwijnen
    Herwijnen is a village in the Dutch province of Gelderland, known as a small rural community along the River Waal.
  • D. Oversticht
    Oversticht was a medieval territorial region in the northern Low Countries that roughly corresponds to much of the modern Dutch province of Overijssel and surrounding areas.
  • E. Het Scheur
    Het Scheur is a major distributary channel of the Rhine–Meuse river system in the Netherlands, forming part of the waterway connection between Rotterdam and the North Sea.
  • 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_69a4948331fc8190b531ac9bec71c491 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be08157c8190b248bb75b922644f completed March 1, 2026, 10:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac8322425c81909cc206b122416c43 completed March 7, 2026, 7:57 p.m.
Created at: March 1, 2026, 7:46 p.m.