Triple
T3561625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 MLS Cup |
E75351
|
entity |
| Predicate | wentToOvertime |
P5853
|
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: [1996 MLS Cup, wentToOvertime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wentToOvertime Context triple: [1996 MLS Cup, wentToOvertime, true]
-
A.
overtimePlayed
chosen
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
-
B.
finalAfterExtraTime
Indicates that the final outcome or result is determined after an additional period of extra time beyond the regular duration.
-
C.
heldOver
Indicates that something has been continued, carried forward, or extended in effect or duration beyond its original or expected time.
-
D.
overtimePeriodCount
Indicates the number of overtime periods that occurred or are allocated in a given event or context.
-
E.
overtimeRule
Indicates the rule or policy that defines when and how overtime work is calculated or applied.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc08bdde88190915d2f6ddf26e00e |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.