Triple
T18844412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carling Knockout Cup |
E460879
|
entity |
| Predicate | decidesWinnerBy |
P125394
|
FINISHED |
| Object | knockout ties |
—
|
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: knockout ties | Statement: [Carling Knockout Cup, decidesWinnerBy, knockout ties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidesWinnerBy Context triple: [Carling Knockout Cup, decidesWinnerBy, knockout ties]
-
A.
determinesChampionBy
Indicates that one entity establishes or decides which entity is the champion, typically as the outcome of a competition or evaluation.
-
B.
decidingGameWinner
Indicates that an event, action, or process determines which participant is the winner of a game.
-
C.
wasDecidedBy
Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
-
D.
mainWinner
Indicates that one entity is the primary or overall winner in a competition, contest, or comparative outcome relative to others.
-
E.
deciderInKnockout
chosen
Indicates that an entity serves as the deciding factor or tiebreaker in determining the outcome of a knockout-stage contest or match.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ed944c81908592f0c34e5727a0 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.