Triple
T14976869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley Parade |
E373470
|
entity |
| Predicate | hasStand |
P6313
|
FINISHED |
| Object | Kop Stand |
E457359
|
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: Kop Stand | Statement: [Valley Parade, hasStand, Kop Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kop Stand Context triple: [Valley Parade, hasStand, Kop Stand]
-
A.
Kop Stand
Kop Stand is a spectator terrace at Windsor Park stadium, traditionally associated with the most vocal home supporters.
-
B.
Kop Stand
chosen
Kop Stand is a prominent all-seater stand at Sheffield United’s Bramall Lane stadium, traditionally housing some of the club’s most vocal supporters.
-
C.
Kop Stand
Kop Stand is a traditional, usually single-tiered terrace-style stand commonly found behind one of the goals at British football grounds, known for housing some of the most vocal home supporters.
-
D.
Kop Stand
Kop Stand is a spectator terrace at Prenton Park, home of Tranmere Rovers Football Club, traditionally housing some of the club’s most vocal supporters.
-
E.
Kop Stand
Kop Stand is a prominent spectator stand at St Andrew's Stadium, home of Birmingham City Football Club.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6fbd138819092254ea37388026c |
completed | April 15, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe8beca6d88190a0c1adb18c9f2ac4 |
completed | May 9, 2026, 1:20 a.m. |
Created at: April 10, 2026, 2:51 a.m.