Triple
T23219036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Call Stadium |
E580833
|
entity |
| Predicate | hasStand |
P6313
|
FINISHED |
| Object | South Stand |
—
|
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: South Stand | Statement: [One Call Stadium, hasStand, South Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: South Stand Context triple: [One Call Stadium, hasStand, South Stand]
-
A.
South Stand
South Stand is a spectator seating section within Philips Stadion, the home ground of Dutch football club PSV Eindhoven.
-
B.
South Stand
chosen
South Stand is a spectator seating section within Colchester United’s Colchester Community Stadium, typically accommodating home supporters during football matches.
-
C.
South Stand
South Stand is a spectator seating section located at the southern end of Pride Park Stadium, home of Derby County Football Club.
-
D.
South Stand
The South Stand is a spectator seating area at Rodney Parade stadium, used primarily for watching rugby and football matches.
-
E.
South Stand
South Stand is a spectator seating section of Kings Park Stadium, a major rugby and sports venue in Durban, South Africa.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f191675de48190858907872a065c56 |
completed | April 29, 2026, 5:04 a.m. |
Created at: April 17, 2026, 4:08 p.m.