Triple
T37003589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota high school football state tournament |
E915721
|
entity |
| Predicate | venueForChampionshipGames |
P186900
|
FINISHED |
| Object | U.S. Bank Stadium |
—
|
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: U.S. Bank Stadium | Statement: [Minnesota high school football state tournament, venueForChampionshipGames, U.S. Bank Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueForChampionshipGames Context triple: [Minnesota high school football state tournament, venueForChampionshipGames, U.S. Bank Stadium]
-
A.
sportsVenueFor
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
B.
ArenaBowlVenue
Indicates that a venue served as the location where an ArenaBowl game was held.
-
C.
holdsTournamentsIn
Indicates that an entity organizes or conducts tournaments at or within a specified location.
-
D.
Game1Venue
Indicates the venue or location where the first game (Game1) of a series or event is held.
-
E.
hasSportsTeamVenueFor
Indicates that a venue serves as the home or hosting location for a particular sports team.
- F. None of above. chosen
Provenance (4 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.