Triple
T10779744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullens Road Stand |
E254285
|
entity |
| Predicate | hasSpectatorAreas |
P13691
|
FINISHED |
| Object | home supporters section |
—
|
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: home supporters section | Statement: [Bullens Road Stand, hasSpectatorAreas, home supporters section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpectatorAreas Context triple: [Bullens Road Stand, hasSpectatorAreas, home supporters section]
-
A.
hasSpectatorArea
chosen
Indicates that a location or facility includes a designated area intended for spectators to observe an event or activity.
-
B.
spectatorAreaType
Indicates the specific kind or category of area designated for spectators in a venue or event setting.
-
C.
hasSpectatorAmenities
Indicates that a place or facility provides amenities or features intended for the comfort or convenience of spectators.
-
D.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
E.
hasSpectatorType
Indicates that an event or activity is associated with a particular category or type of spectator.
- 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.