Triple
T21195730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banditland |
E522319
|
entity |
| Predicate | typicalVenueSection |
P97819
|
FINISHED |
| Object | lower bowl of KeyBank Center |
—
|
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: lower bowl of KeyBank Center | Statement: [Banditland, typicalVenueSection, lower bowl of KeyBank Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVenueSection Context triple: [Banditland, typicalVenueSection, lower bowl of KeyBank Center]
-
A.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
B.
typicalVenueSetting
chosen
Indicates the usual or characteristic type of venue or setting in which an event, activity, or interaction typically takes place.
-
C.
featuresVenue
Indicates that one entity includes, hosts, or is associated with a particular venue as part of its offering or context.
-
D.
formerTypicalVenue
Indicates that a location was once the usual or primary venue for an entity’s activities or events, but no longer serves in that typical role.
-
E.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7333bd7a0819084bbd1d6c111bc65 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:08 p.m.