Triple
T10779796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park End Stand |
E254287
|
entity |
| Predicate | hasSpectatorAccess |
P13691
|
FINISHED |
| Object | turnstiles at Goodison Park |
—
|
LITERAL 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: turnstiles at Goodison Park | Statement: [Park End Stand, hasSpectatorAccess, turnstiles at Goodison Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpectatorAccess Context triple: [Park End Stand, hasSpectatorAccess, turnstiles at Goodison Park]
-
A.
hasSpectatorType
Indicates that an event or activity is associated with a particular category or type of spectator.
-
B.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
C.
spectatorRestrictions
Indicates limitations, conditions, or rules governing who may be present as spectators and under what circumstances.
-
D.
hasSpectatorArea
chosen
Indicates that a location or facility includes a designated area intended for spectators to observe an event or activity.
-
E.
audienceAccess
Indicates that one entity has permission or ability to access, view, or engage with a particular audience associated with another entity.
- F. None of above.
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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732c384bc81908f503f3a2e0503a4 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.