Triple
T23219034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Call Stadium |
E580833
|
entity |
| Predicate | hasStand |
P6313
|
FINISHED |
| Object | North 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: North Stand | Statement: [One Call Stadium, hasStand, North Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: North Stand Context triple: [One Call Stadium, hasStand, North Stand]
-
A.
North Stand
North Stand is a spectator seating section of Hillsborough Stadium, home of Sheffield Wednesday Football Club.
-
B.
North Stand
chosen
North Stand is a spectator seating section located behind one of the goals at Keepmoat Stadium, home of Doncaster Rovers FC.
-
C.
North Stand
North Stand is a spectator seating section of the Macron Stadium, home ground of Bolton Wanderers Football Club in Bolton, England.
-
D.
North Stand
The North Stand is a spectator section of Borussia Dortmund’s Westfalenstadion, known for hosting part of the stadium’s passionate home support.
-
E.
North Stand
North Stand is a spectator seating section at Silverlake Stadium, home of Eastleigh F.C. in Hampshire, England.
- 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.