Triple
T18829313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owlerton Stadium |
E460478
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | North Stand |
—
|
NE NERFINISHED |
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: North Stand | Statement: [Owlerton Stadium, hasPart, North Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: North Stand Context triple: [Owlerton Stadium, hasPart, North Stand]
-
A.
North Stand
North Stand is a spectator seating section within Parc y Scarlets stadium, providing views of the pitch from the northern side.
-
B.
North Stand
chosen
North Stand is a spectator seating section of Hillsborough Stadium, home of Sheffield Wednesday Football Club.
-
C.
North Stand
North Stand is a spectator seating section located behind one of the goals at Keepmoat Stadium, home of Doncaster Rovers FC.
-
D.
North Stand
North Stand is a spectator seating section at Rodney Parade stadium, providing views of the pitch for fans during sporting events.
-
E.
North Stand
North Stand is a spectator seating section located behind one of the goals at King Power Stadium, home of Leicester City Football Club.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 10, 2026, 11:56 a.m.