Triple
T12986775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howard J. Lamade Stadium |
E321787
|
entity |
| Predicate | hasTypeOfSpectatorArea |
P31261
|
FINISHED |
| Object | fixed grandstand seating |
—
|
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: fixed grandstand seating | Statement: [Howard J. Lamade Stadium, hasTypeOfSpectatorArea, fixed grandstand seating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfSpectatorArea Context triple: [Howard J. Lamade Stadium, hasTypeOfSpectatorArea, fixed grandstand seating]
-
A.
hasSpectatorArea
Indicates that a location or facility includes a designated area intended for spectators to observe an event or activity.
-
B.
spectatorAreaType
chosen
Indicates the specific kind or category of area designated for spectators in a venue or event setting.
-
C.
hasSpectatorType
Indicates that an event or activity is associated with a particular category or type of spectator.
-
D.
hasPlayAreaType
Indicates the specific kind or category of play area associated with an entity (e.g., indoor, outdoor, playground type).
-
E.
hasSpectatorAmenities
Indicates that a place or facility provides amenities or features intended for the comfort or convenience of 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:40 p.m.