Triple
T28107166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFA Cup |
E710394
|
entity |
| Predicate | matchOutcomeDecider |
P68822
|
FINISHED |
| Object | extra time |
—
|
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: extra time | Statement: [CFA Cup, matchOutcomeDecider, extra time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchOutcomeDecider Context triple: [CFA Cup, matchOutcomeDecider, extra time]
-
A.
decidingGameWinner
Indicates that an event, action, or process determines which participant is the winner of a game.
-
B.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
-
C.
matchOutcomeRule
Indicates the rule or condition that determines the outcome of a match between participants.
-
D.
finalMatchDetermines
Indicates that the outcome of a final match decides or establishes a particular result, status, or consequence for the related entities.
-
E.
finalMatchDecidedBy
chosen
Indicates that the outcome of a final match is determined by a specific method, event, or deciding factor.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 9:09 p.m.