Triple
T14910400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Border Battle |
E371245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intercollegiate athletic series |
C24322
|
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: intercollegiate athletic series Context triple: [Border Battle, instanceOf, intercollegiate athletic series]
-
A.
intercollegiate athletic events
chosen
Intercollegiate athletic events are organized sports competitions in which teams or individuals representing different colleges or universities compete under established rules and governing bodies.
-
B.
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.
-
C.
NCAA sport
An NCAA sport is an organized athletic activity governed by the National Collegiate Athletic Association in which college teams compete under standardized rules and eligibility requirements.
-
D.
university sports competitions
University sports competitions are organized athletic events in which teams or individuals representing higher education institutions compete under standardized rules to promote physical excellence, school spirit, and intercollegiate rivalry.
-
E.
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.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:26 a.m.