Triple
T222385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supporters' Shield race |
E4243
|
entity |
| Predicate | winnerQualification |
P2691
|
FINISHED |
| Object | CONCACAF Champions Cup berth |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: CONCACAF Champions Cup berth | Statement: [Supporters' Shield race, winnerQualification, CONCACAF Champions Cup berth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerQualification Context triple: [Supporters' Shield race, winnerQualification, CONCACAF Champions Cup berth]
-
A.
winnerQualifiedFor
chosen
Indicates that the entity identified as the winner has earned or met the conditions required to qualify for a subsequent stage, event, or status.
-
B.
awardsQualificationTo
Indicates that one entity grants or confers a qualification, certification, or credential to another entity.
-
C.
winnerPoints
Indicates the number of points earned by the winning participant or entity in a competition or event.
-
D.
winnerPlaysIn
Indicates that the entity identified as the winner of a contest or match participates in a subsequent game, round, or event.
-
E.
winnerCount
Indicates the number of entities that are designated as winners in a given context or event.
- F. None of above.
Provenance (3 batches)
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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c705fd88190bfee7f5e1f7cee17 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5617788190814358aee3f7ae37 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.