Triple
T8005656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Super Cup |
E186356
|
entity |
| Predicate | extraTimePolicy |
P80515
|
FINISHED |
| Object | usually no 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: usually no extra time | Statement: [German Super Cup, extraTimePolicy, usually no extra time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extraTimePolicy Context triple: [German Super Cup, extraTimePolicy, usually no extra time]
-
A.
overtimePolicy
Indicates the rules or conditions governing when and how overtime work is allowed, calculated, and compensated between an employer and employees.
-
B.
usesExtraTime
Indicates that an entity makes use of additional time beyond an initial or standard allotted period to perform or complete an action.
-
C.
overtimeRule
Indicates the rule or policy that defines when and how overtime work is calculated or applied.
-
D.
overtimePeriodDuration
Indicates the length of time that an overtime period lasts.
-
E.
allowsOvertime
Indicates that one entity permits another entity to work beyond standard or scheduled time limits.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:18 p.m.