Triple
T13296076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Clark Stadium |
E316685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high school football stadium |
C27402
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: high school football stadium Context triple: [Dutch Clark Stadium, instanceOf, high school football stadium]
-
A.
American football field
chosen
An American football field is a rectangular, 120-yard-long (including two 10-yard end zones) and 53⅓-yard-wide playing surface marked with yard lines, hash marks, and goalposts at each end, used for organized American football games.
-
B.
football stadium stands
A football stadium stands is the tiered seating structure surrounding the pitch, designed to accommodate spectators with clear views of the game and associated amenities.
-
C.
American football training facility
An American football training facility is a specialized complex equipped with fields, weight rooms, meeting spaces, and technology designed to support the physical, tactical, and strategic development of football players and teams.
-
D.
Canadian football stadium
A Canadian football stadium is a large outdoor or domed sports venue specifically designed and equipped to host Canadian football games, including a full-sized CFL-regulation field, spectator seating, and related facilities.
-
E.
Australian rules football stadium
An Australian rules football stadium is a large, oval-shaped sports venue specifically designed and equipped to host Australian rules football matches, including playing field, spectator seating, and supporting facilities.
- F. None of above.
Provenance (1 batch)
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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:28 p.m.