Triple
T18470922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Stand |
E451296
|
entity |
| Predicate | hasName |
P744
|
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: [North Stand, hasName, North Stand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: North Stand Context triple: [North Stand, hasName, North Stand]
-
A.
North Stand
The North Stand is one of the main spectator sections of Dublin’s Aviva Stadium, providing tiered seating behind one of the goals for rugby and football matches.
-
B.
North Stand
North Stand is a spectator seating section of the Peninsula Stadium, home ground of Salford City FC in Greater Manchester, England.
-
C.
North Stand
North Stand is a spectator seating section of Hillsborough Stadium, home of Sheffield Wednesday Football Club.
-
D.
North Stand
North Stand is a spectator seating section located behind one of the goals at Keepmoat Stadium, home of Doncaster Rovers FC.
-
E.
North Stand
North Stand is a spectator seating section at Rodney Parade stadium, providing views of the pitch for fans during sporting events.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5305f428c81909980bd30d150e7dd |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 11:34 a.m.