Triple

T13628020
Position Surface form Disambiguated ID Type / Status
Subject Schie River E325637 entity
Predicate flowsThrough P225 FINISHED
Object Overschie E382251 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: Overschie | Statement: [Schie River, flowsThrough, Overschie]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Overschie
Context triple: [Schie River, flowsThrough, Overschie]
  • A. Overschie chosen
    Overschie is a historic neighborhood and former village now incorporated into the city of Rotterdam in the Netherlands.
  • B. Overhoeks
    Overhoeks is a modern waterfront district in Amsterdam known for its contemporary architecture, cultural venues, and redevelopment of former industrial land along the IJ river.
  • C. Oudezijde
    Oudezijde is a historic quarter in Amsterdam’s medieval city center, known for its canals, old churches, and traditional urban fabric.
  • D. Vriezekoop
    Vriezekoop is a small village in the Dutch province of South Holland, known for its rural character and location along the Westeinderplassen near Leimuiden.
  • E. Overveen
    Overveen is a village in the Dutch province of North Holland, known for its proximity to the North Sea coast and the nearby dunes and forests.
  • 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_69d8076aae28819092cf636190ee5529 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbbe9d803481908101def32817b0eb completed April 12, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69f77fa6a46881909d381d76d391f5b7 completed May 3, 2026, 5:02 p.m.
Created at: April 9, 2026, 9:51 p.m.