Triple
T3604700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GelreDome |
E76341
|
entity |
| Predicate | homeVenueOf |
P890
|
FINISHED |
| Object | Vitesse Arnhem |
E310498
|
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: Vitesse Arnhem | Statement: [GelreDome, homeVenueOf, Vitesse Arnhem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vitesse Arnhem Context triple: [GelreDome, homeVenueOf, Vitesse Arnhem]
-
A.
Vitesse Arnhem
chosen
Vitesse Arnhem is a professional football club from Arnhem, Netherlands, known for competing in the Dutch Eredivisie.
-
B.
Arnhem
Arnhem is a city in the eastern Netherlands best known as the site of a major World War II battle during Operation Market Garden.
-
C.
Arnhem–Nijmegen railway
The Arnhem–Nijmegen railway is a Dutch rail line in the province of Gelderland that connects the cities of Arnhem and Nijmegen as part of the national railway network.
-
D.
Arnhemmer
An Arnhemmer is a resident or native of the Dutch city of Arnhem in the province of Gelderland.
-
E.
Diksmuide
Diksmuide is a historic town in western Belgium known for its World War I battlefields and memorials, particularly the Yser Tower.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1e07bc481908d9fce18d36d8e0d |
completed | March 8, 2026, 6:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b40320a0308190b2f358fe1488ed98 |
completed | March 13, 2026, 12:29 p.m. |
Created at: March 8, 2026, 3:22 p.m.