Triple
T13398017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brentford Community Stadium |
E319749
|
entity |
| Predicate | hasStand |
P6313
|
FINISHED |
| Object | South Stand |
E319751
|
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: [Brentford Community Stadium, hasStand, South Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: South Stand Context triple: [Brentford Community Stadium, hasStand, South Stand]
-
A.
South Stand
chosen
South Stand is a spectator seating section within the Gtech Community Stadium, home to Brentford Football Club in London.
-
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 within Colchester United’s Colchester Community Stadium, typically accommodating home supporters during football matches.
-
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 (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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d9e7348190844e11dd6cbd13b0 |
completed | April 12, 2026, 1:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f73071c0b88190bca3b15ea11c7491 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:34 p.m.