Triple
T8005657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Super Cup |
E186356
|
entity |
| Predicate | penaltyShootoutPolicy |
P12108
|
FINISHED |
| Object | used to decide winner if draw after 90 minutes |
—
|
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: used to decide winner if draw after 90 minutes | Statement: [German Super Cup, penaltyShootoutPolicy, used to decide winner if draw after 90 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penaltyShootoutPolicy Context triple: [German Super Cup, penaltyShootoutPolicy, used to decide winner if draw after 90 minutes]
-
A.
penaltyShootoutOccurred
Indicates that a penalty shootout took place to decide the outcome of a match or contest.
-
B.
penaltyShootOutLocation
Indicates the specific place or venue where a penalty shoot-out event occurs.
-
C.
usesPenaltyShootouts
chosen
Indicates that the outcome of a match or competition is decided by conducting penalty shootouts.
-
D.
penaltyShootoutScore
Indicates the number of goals each side scored during a penalty shootout used to decide a tied match.
-
E.
penaltyShootoutWinner
Indicates that one competitor or team is the winner of a match decided by a penalty shootout.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf72fc08190aa78b97c1ab92f90 |
completed | March 31, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:18 p.m.