Triple
T19506762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Korenbloem (Oploo) |
E488041
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Oploo |
—
|
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: Oploo | Statement: [De Korenbloem (Oploo), locatedIn, Oploo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oploo Context triple: [De Korenbloem (Oploo), locatedIn, Oploo]
-
A.
Oploo
chosen
Oploo is a village in the Dutch province of North Brabant, known for its rural character and historic windmill.
-
B.
Toorop
Toorop is the surname of Jan Toorop, a prominent Dutch-Indonesian painter associated with Symbolism and Art Nouveau.
-
C.
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.
-
D.
Loenersloot
Loenersloot is a small village in the Dutch province of Utrecht, known for its historic Loenersloot Castle and rural setting along the river Vecht.
-
E.
Ruurlo
Ruurlo is a village in the Dutch province of Gelderland, known for its historic estates and rural character.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63511fc688190bd1474406060fa1b |
completed | April 20, 2026, 2:15 p.m. |
Created at: April 10, 2026, 1:40 p.m.