Triple
T593352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Farm Center |
E17324
|
entity |
| Predicate | isMajorVenueFor |
P13342
|
FINISHED |
| Object | Big Ten Conference basketball games |
—
|
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: Big Ten Conference basketball games | Statement: [State Farm Center, isMajorVenueFor, Big Ten Conference basketball games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorVenueFor Context triple: [State Farm Center, isMajorVenueFor, Big Ten Conference basketball games]
-
A.
hasMajorVenue
chosen
Indicates that an entity is associated with a primary or principal venue where its main activities or events take place.
-
B.
venueComplex
Indicates that one venue is a complex or larger facility that contains or encompasses another venue.
-
C.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
D.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
E.
isMajorAttractionIn
Indicates that something is a primary or highly significant attraction within a particular place 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bbcaf5c81908de4e27096d3da13 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cd7d3c8190af008acf34a2293b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.