Triple
T16323236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Athletics track and field rules as adapted by NCAA |
E396349
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | track and field regulations |
C1114
|
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: track and field regulations Context triple: [World Athletics track and field rules as adapted by NCAA, instanceOf, track and field regulations]
-
A.
sports regulations
chosen
Sports regulations are the formal rules and standards that govern how a sport is played, officiated, and administered to ensure fairness, safety, and consistency in competition.
-
B.
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.
-
C.
international track and field competition
An international track and field competition is a globally organized sporting event where athletes from multiple countries compete in a range of running, jumping, and throwing disciplines under standardized rules.
-
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.
sports rulebook
A sports rulebook is a formal document that defines the official rules, procedures, and standards governing how a particular sport is played, officiated, and organized.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:06 a.m.