Triple
T4683470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillsborough Stadium |
E103859
|
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: [Hillsborough Stadium, hasStand, Kop Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kop Stand Context triple: [Hillsborough Stadium, 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 prominent spectator stand at St Andrew's Stadium, home of Birmingham City Football Club.
-
D.
Bar Kosiba
Bar Kosiba is another name for Simon bar Kokhba, the Jewish military leader who led the Bar Kokhba revolt against the Roman Empire in the 2nd century CE.
-
E.
Papekop (partly)
Papekop (partly) is a small village in the Dutch province of South Holland, known for its rural character and location between larger towns such as Oudewater and Woerden.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd638130a08190876c5829c0488758 |
completed | March 20, 2026, 3:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be03b07664819097d959fde1b0585b |
completed | March 21, 2026, 2:34 a.m. |
Created at: March 20, 2026, 1:16 p.m.