Triple
T18732900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division III East Region |
E458081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collegiate sports region |
C39931
|
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: collegiate sports region Context triple: [NCAA Division III East Region, instanceOf, collegiate sports region]
-
A.
collegiate athletic conference
A collegiate athletic conference is an organized group of colleges and universities that compete against each other in intercollegiate sports under shared rules, governance, and scheduling agreements.
-
B.
NCAA Division II athletic region
An NCAA Division II athletic region is a geographically defined grouping of Division II member institutions organized to structure competition, championships, and administrative oversight within the NCAA framework.
-
C.
NJCAA region
An NJCAA region is a geographically defined grouping of two-year colleges organized under the National Junior College Athletic Association to structure intercollegiate athletic competition and administration.
-
D.
collegiate athletic conference sport
A collegiate athletic conference sport is a competitive athletic activity officially sponsored and organized by a college sports conference, with member institutions fielding teams that compete under shared rules, schedules, and championship structures.
-
E.
NCAA Division III region
chosen
An NCAA Division III region is a geographically defined grouping of Division III member institutions used by the NCAA to organize competition, rankings, and championships within specific sports.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:51 a.m.