Triple
T8019843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Stadium Corporation |
E186710
|
entity |
| Predicate | operatedVenueType |
P43750
|
FINISHED |
| Object | indoor arena |
—
|
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: indoor arena | Statement: [Chicago Stadium Corporation, operatedVenueType, indoor arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedVenueType Context triple: [Chicago Stadium Corporation, operatedVenueType, indoor arena]
-
A.
venueTypeOperated
chosen
Indicates that an entity operates or manages a venue of a specified type.
-
B.
operatesVenue
Indicates that one entity manages and runs the day-to-day operations of a particular venue.
-
C.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
D.
locatedInOperatedVenue
Indicates that an entity is situated within a venue that is managed or operated by a specified agent or organization.
-
E.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8bc90081909f6f5878e6f1f241 |
completed | March 31, 2026, 3:24 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.