Triple
T17716151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schie |
E442204
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Oude Schie |
—
|
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: Oude Schie | Statement: [Schie, hasPart, Oude Schie]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oude Schie Context triple: [Schie, hasPart, Oude Schie]
-
A.
Oude Schie
chosen
Oude Schie is a historic canalized branch of the Schie River in the Netherlands, known for its role in regional transport and water management between Delft and surrounding areas.
-
B.
Oud-Waterschei
Oud-Waterschei is a neighborhood of the Belgian city of Genk, historically known for its coal mining heritage and associated garden city architecture.
-
C.
Goudriaanse Vliet
Goudriaanse Vliet is a small Dutch waterway or canal associated with the village of Goudriaan in the Netherlands.
-
D.
Oberscheld
Oberscheld is a village and district of the town of Dillenburg in the Lahn-Dill-Kreis of Hesse, Germany.
-
E.
Dijle
The Dijle is a river in central Belgium that flows through cities such as Leuven and Mechelen before joining other waterways that ultimately form part of the Rhine–Meuse river system.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47480955481908fa0d3d34aaedd48 |
completed | April 19, 2026, 6:21 a.m. |
Created at: April 10, 2026, 10:06 a.m.