Triple
T3205311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2020 |
E67146
|
entity |
| Predicate | regulationDurationMinutes |
P25687
|
FINISHED |
| Object | 90 |
—
|
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: 90 | Statement: [MLS Cup 2020, regulationDurationMinutes, 90]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulationDurationMinutes Context triple: [MLS Cup 2020, regulationDurationMinutes, 90]
-
A.
regulationMinutes
chosen
Indicates the number of minutes played during the standard regulation period of a game, excluding any overtime or extra periods.
-
B.
regulatesTimeFor
Indicates that one entity controls, influences, or sets the timing or schedule of another entity’s activities or processes.
-
C.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
D.
banDurationApproximate
Indicates that the duration of a ban is known only approximately rather than as an exact, precise time period.
-
E.
hasOfficialDuration
Indicates the formally defined length of time associated with an event, process, or entity.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa559848819082d1e61f586278dd |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.