Triple
T36740172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Athletics Indoor Championships |
E907587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | indoor athletics competition |
C29291
|
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 athletics competition Context triple: [European Athletics Indoor Championships, instanceOf, indoor athletics competition]
-
A.
international track and field competition
chosen
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.
-
B.
indoor tennis competition
An indoor tennis competition is an organized series of tennis matches held within an enclosed facility, typically featuring controlled environmental conditions and structured formats such as tournaments or leagues.
-
C.
indoor athletic facility
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.
-
D.
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.
-
E.
track and field event
A track and field event is an organized athletic competition in which participants perform running, jumping, or throwing disciplines under standardized rules and conditions.
- 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.