Triple
T13270302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leverone Field House |
E316037
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | indoor track and field facility |
C239
|
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: indoor track and field facility Context triple: [Leverone Field House, instanceOf, indoor track and field facility]
-
A.
indoor athletic facility
chosen
An indoor athletic facility is a covered, climate-controlled space equipped with specialized areas and equipment designed to support a variety of sports, fitness activities, and physical training programs year-round.
-
B.
sports and recreation facility
A sports and recreation facility is a place designed and equipped for individuals or groups to engage in physical activities, sports, exercise, and leisure pursuits.
-
C.
college track and field competition
A college track and field competition is an organized athletic meet where collegiate athletes represent their institutions in a variety of running, jumping, and throwing events under standardized rules and scoring.
-
D.
college track and field championship
A college track and field championship is a competitive athletic event where collegiate teams and athletes contest a series of track races and field events to determine individual and team titles at a conference, regional, or national level.
-
E.
Olympic competition venue area
An Olympic competition venue area is a designated, secure space that includes the field of play and its immediate surroundings where official Olympic events are conducted according to sport-specific standards.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:26 p.m.