Triple
T4679253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Rhine |
E103757
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Alphen aan den Rijn |
E167487
|
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: Alphen aan den Rijn | Statement: [Old Rhine, passesNear, Alphen aan den Rijn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alphen aan den Rijn Context triple: [Old Rhine, passesNear, Alphen aan den Rijn]
-
A.
Alphen aan den Rijn
chosen
Alphen aan den Rijn is a Dutch town and municipality situated along the Oude Rijn river in the western Netherlands.
-
B.
Eindhoven
Eindhoven is a major city in the southern Netherlands known for its industrial and technological significance, particularly as a hub for electronics and design.
-
C.
Tilburg
Tilburg is a city in the southern Netherlands known historically as an industrial and textile center and now as a regional cultural and educational hub.
-
D.
Zoeterwoude
Zoeterwoude is a small Dutch municipality and village known for its rural character and location near Leiden in the province of South Holland.
-
E.
Roosendaal
Roosendaal is a city in the southern Netherlands known as a regional center for commerce and transport near the Belgian border.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd636acffc819094e03c5bb53203d8 |
completed | March 20, 2026, 3:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d160f6855c81909ae0f3f1c041f600 |
completed | April 4, 2026, 7:05 p.m. |
Created at: March 20, 2026, 1:16 p.m.