Triple
T18029856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011–12 CONCACAF Champions League |
E431355
|
entity |
| Predicate | usesExtraTimeInFinal |
P35409
|
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: [2011–12 CONCACAF Champions League, usesExtraTimeInFinal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesExtraTimeInFinal Context triple: [2011–12 CONCACAF Champions League, usesExtraTimeInFinal, true]
-
A.
usesExtraTime
Indicates that an entity makes use of additional time beyond an initial or standard allotted period to perform or complete an action.
-
B.
usesExtraTimeInLaterRounds
Indicates that an entity allocates or consumes additional time during later stages or rounds of an activity, process, or event.
-
C.
extraTimePolicy
Indicates a policy that defines when and how additional time is granted beyond a standard or scheduled duration.
-
D.
finalAfterExtraTime
chosen
Indicates that the final outcome or result is determined after an additional period of extra time beyond the regular duration.
-
E.
usesOvertime
Indicates that one entity makes use of another entity repeatedly or continuously over an extended period of time.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be347f6c8190b324fe74b7dc1764 |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.