Triple
T36410166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota Thunder |
E896853
|
entity |
| Predicate | homeVenueComplex |
P13805
|
FINISHED |
| Object | National Sports Center sports complex |
—
|
NE NERFINISHED |
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: National Sports Center sports complex | Statement: [Minnesota Thunder, homeVenueComplex, National Sports Center sports complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueComplex Context triple: [Minnesota Thunder, homeVenueComplex, National Sports Center sports complex]
-
A.
venueComplex
chosen
Indicates that one venue is a complex or larger facility that contains or encompasses another venue.
-
B.
home venue type
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
-
C.
homeVenueIncludes
Indicates that a specified venue is part of, contained within, or used as a home location by another entity.
-
D.
homeMeetsVenue
Indicates that a home team plays its scheduled match at a specified venue.
-
E.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.