Triple
T16804002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putnam Competition |
E408431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | undergraduate mathematics competition |
C24736
|
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: undergraduate mathematics competition Context triple: [Putnam Competition, instanceOf, undergraduate mathematics competition]
-
A.
student research competition
A student research competition is an event where students present original research projects to be evaluated and ranked by judges based on criteria such as innovation, rigor, and impact.
-
B.
youth competition
chosen
A youth competition is an organized event where young individuals or teams compete in specific activities or disciplines to demonstrate their skills, talents, or knowledge, often within defined age categories.
-
C.
national competition
A national competition is a large-scale contest in which individuals or teams from across an entire country compete under standardized rules to determine top performers or champions in a specific field.
-
D.
competition section
A competition section is a designated part of an event, document, or platform that organizes, presents, and manages information, rules, and results related to specific contests or competitive activities.
-
E.
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.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.