Triple

T17203637
Position Surface form Disambiguated ID Type / Status
Subject Windsor Park, Belfast E417541 entity
Predicate hasStand P6313 FINISHED
Object Kop Stand E413403 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: [Windsor Park, Belfast, hasStand, Kop Stand]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Kop Stand
Context triple: [Windsor Park, Belfast, hasStand, Kop Stand]
  • A. Kop Stand chosen
    Kop Stand is a spectator terrace at Windsor Park stadium, traditionally associated with the most vocal home supporters.
  • B. 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.
  • 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 prominent spectator stand at St Andrew's Stadium, home of Birmingham City Football Club.
  • 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.
  • 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_69d886d6ba8c819093215917b3d01689 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42db11fc881908291bf29cc740e09 completed April 19, 2026, 1:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a015fdc13d88190bbf9e6d1272814d2 completed May 11, 2026, 4:49 a.m.
Created at: April 10, 2026, 5:38 a.m.