Triple
T6794780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eco-Power Stadium |
E156026
|
entity |
| Predicate | hasStand |
P6313
|
FINISHED |
| Object | South Stand |
unclear NED1
|
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: South Stand | Statement: [Eco-Power Stadium, hasStand, South Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: South Stand Context triple: [Eco-Power Stadium, hasStand, South Stand]
-
A.
South Stand
South Stand is the massive single-tier home end of Tottenham Hotspur Stadium, designed to create an intense, wall-of-sound atmosphere behind one of the goals.
-
B.
South Stand
South Stand is a spectator seating section within Philips Stadion, the home ground of Dutch football club PSV Eindhoven.
-
C.
South Stand
South Stand is a spectator seating section of Falkirk Stadium, used by fans attending football matches and other events.
-
D.
South Stand
South Stand is a spectator seating section located at New Douglas Park, the home stadium of Hamilton Academical FC in Scotland.
-
E.
South Stand
South Stand is a spectator seating section within Parc y Scarlets stadium, providing views of rugby and other events held there.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2c59648819081736d27d52d957f |
completed | March 27, 2026, 6:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c71a9354448190890846c2e84bb22c |
completed | March 28, 2026, 12:02 a.m. |
Created at: March 27, 2026, 2:15 p.m.