Triple
T23625765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League 2013–14 |
E583458
|
entity |
| Predicate | usesExtraTimeInKnockout |
P19892
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [UEFA Champions League 2013–14, usesExtraTimeInKnockout, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesExtraTimeInKnockout Context triple: [UEFA Champions League 2013–14, usesExtraTimeInKnockout, true]
-
A.
usesExtraTimeInLaterRounds
Indicates that an entity allocates or consumes additional time during later stages or rounds of an activity, process, or event.
-
B.
usesExtraTime
chosen
Indicates that an entity makes use of additional time beyond an initial or standard allotted period to perform or complete an action.
-
C.
finalAfterExtraTime
Indicates that the final outcome or result is determined after an additional period of extra time beyond the regular duration.
-
D.
extraTimePolicy
Indicates a policy that defines when and how additional time is granted beyond a standard or scheduled duration.
-
E.
extraTimeHalfLength
Indicates the duration or length of an extra-time half period within a timed event 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17c993c8190bf9ee3201869d240 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.