Triple
T23219047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Call Stadium |
E580833
|
entity |
| Predicate | hasAllSeatedAreas |
P61488
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [One Call Stadium, hasAllSeatedAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAllSeatedAreas Context triple: [One Call Stadium, hasAllSeatedAreas, yes]
-
A.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
B.
individualSeats
chosen
Indicates that an entity provides or consists of separate, single-person seating positions rather than shared or bench-style seating.
-
C.
hasShelteredSeating
Indicates that an entity provides seating that is protected from weather or other external elements.
-
D.
hasFlexibleSeating
Indicates that an entity provides seating arrangements that can be easily rearranged, adjusted, or reconfigured to suit different uses or preferences.
-
E.
hasSeatingNearby
Indicates that suitable seating is available in close proximity to the referenced entity or location.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f191675de48190858907872a065c56 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.