Triple
T18777819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Profile in Courage Essay Contest for high school students |
E459177
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high school student 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: high school student competition Context triple: [Profile in Courage Essay Contest for high school students, instanceOf, high school student competition]
-
A.
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.
-
B.
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.
-
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.
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.
-
E.
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.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:52 a.m.