Triple
T20920952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | men's high jump at the 1936 Summer Olympics |
E515205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | men's high jump competition |
C23510
|
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: men's high jump competition Context triple: [men's high jump at the 1936 Summer Olympics, instanceOf, men's high jump competition]
-
A.
high jumper
A high jumper is an athlete who attempts to leap over a horizontal bar at progressively greater heights using specialized techniques and approaches.
-
B.
men’s volleyball competition
A men’s volleyball competition is an organized sporting event in which male teams compete in structured matches, following official volleyball rules, to determine rankings or a champion.
-
C.
high school sports competition
A high school sports competition is an organized event where student athletes from one or more schools compete in structured athletic contests governed by standardized rules and regulations.
-
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.
athletics meeting
chosen
An athletics meeting is an organized sports event where athletes compete in various track and field disciplines under standardized rules and scheduling.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:48 p.m.