Triple
T8059402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicarage Road |
E188080
|
entity |
| Predicate | hasAwaySupporterArea |
P13691
|
FINISHED |
| Object | Vicarage Road Stand away 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: Vicarage Road Stand away section | Statement: [Vicarage Road, hasAwaySupporterArea, Vicarage Road Stand away section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAwaySupporterArea Context triple: [Vicarage Road, hasAwaySupporterArea, Vicarage Road Stand away section]
-
A.
hasSpectatorArea
chosen
Indicates that a location or facility includes a designated area intended for spectators to observe an event or activity.
-
B.
hasStandingArea
Indicates that an entity includes or provides a designated area where people can stand.
-
C.
supportsAwayMatchesOf
Indicates that one entity provides backing, resources, or endorsement specifically for the away matches played by another entity.
-
D.
hasTicketCollectorArea
Indicates that a location or facility includes a designated area where ticket collectors operate or perform their duties.
-
E.
hasBleacherSeating
Indicates that a venue or location is equipped with bleacher-style seating for spectators.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fcaa8b8819099267564b6542547 |
completed | March 31, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.