Triple
T18829315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owlerton Stadium |
E460478
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object |
Kop Stand
Kop Stand is a traditional, usually steeply tiered football stadium terrace or stand commonly associated with passionate home supporters.
|
E704202
|
NE FINISHED |
How this triple was built (4 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: [Owlerton Stadium, hasPart, Kop Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kop Stand Context triple: [Owlerton Stadium, hasPart, Kop Stand]
-
A.
Kop Stand
Kop Stand is a prominent spectator stand at St Andrew's Stadium, home of Birmingham City Football Club.
-
B.
Kop Stand
Kop Stand is a spectator terrace at Windsor Park stadium, traditionally associated with the most vocal home supporters.
-
C.
Kop Stand
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.
-
D.
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.
-
E.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kop Stand Triple: [Owlerton Stadium, hasPart, Kop Stand]
Generated description
Kop Stand is a traditional, usually steeply tiered football stadium terrace or stand commonly associated with passionate home supporters.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Kop Stand Target entity description: Kop Stand is a traditional, usually steeply tiered football stadium terrace or stand commonly associated with passionate home supporters.
-
A.
Kop Stand
Kop Stand is a prominent spectator stand at St Andrew's Stadium, home of Birmingham City Football Club.
-
B.
Kop Stand
Kop Stand is a spectator terrace at Windsor Park stadium, traditionally associated with the most vocal home supporters.
-
C.
Kop Stand
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.
-
D.
Kop Stand
chosen
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.
-
E.
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.
- F. None of above.
Provenance (5 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a9981be88190b709c0e72ad3f7e6 |
completed | April 20, 2026, 4:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a055bd216d881908bee50901656372e |
completed | May 14, 2026, 5:21 a.m. |
| NEDg | Description generation | batch_6a0561e6500c8190b42d8257180ad7a6 |
completed | May 14, 2026, 5:47 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a05623b880c81908fedf88e6a79ac31 |
completed | May 14, 2026, 5:48 a.m. |
Created at: April 10, 2026, 11:56 a.m.