Triple
T23063736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | river IJssel |
E574975
|
entity |
| Predicate | hasTownOnBank |
P847
|
FINISHED |
| Object | Doesburg |
—
|
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: Doesburg | Statement: [river IJssel, hasTownOnBank, Doesburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Doesburg Context triple: [river IJssel, hasTownOnBank, Doesburg]
-
A.
Doesburg
chosen
Doesburg is a historic city in the Dutch province of Gelderland, known for its well-preserved medieval center and location at the confluence of the IJssel and Oude IJssel rivers.
-
B.
Vredenburg
Vredenburg is a former name of the Muziekcentrum Vredenburg, a prominent concert and music venue in Utrecht, Netherlands.
-
C.
Vredenburg
Vredenburg is a town on South Africa’s West Coast that serves as a regional commercial and service hub near Saldanha Bay.
-
D.
Batenburg
Batenburg is a small historic town in the Dutch province of Gelderland, known for its medieval castle ruins and picturesque setting along the river Maas.
-
E.
Dieburg
Dieburg is a small historic town in the German state of Hesse, known for its medieval old town and regional administrative role.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f189a1f49c81909db7e0473ec2bb1b |
completed | April 29, 2026, 4:31 a.m. |
Created at: April 17, 2026, 3:55 p.m.