Triple
T24469438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winning Alliance |
E617058
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | competition recognition |
C49038
|
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: competition recognition Context triple: [Winning Alliance, instanceOf, competition recognition]
-
A.
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.
-
B.
performance competition
A performance competition is an organized event where individuals or teams present artistic, athletic, or skill-based performances to be evaluated and ranked by judges or audience criteria.
-
C.
competition strand
A competition strand is a distinct category or track within a larger competitive event that groups participants by specific criteria such as skill level, theme, or format.
-
D.
international competition
An international competition is a structured event in which individuals or teams from multiple countries compete under standardized rules to determine relative excellence in a specific field or activity.
-
E.
intellectual competition
An intellectual competition is an organized event in which individuals or teams challenge each other’s knowledge, reasoning, or problem-solving abilities within defined rules and criteria for evaluation.
- F. None of above. chosen
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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:20 a.m.