Triple
T1150733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2000 |
E23669
|
entity |
| Predicate | isFinalMatchOf |
P21957
|
FINISHED |
| Object | 2000 MLS season |
—
|
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: 2000 MLS season | Statement: [MLS Cup 2000, isFinalMatchOf, 2000 MLS season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFinalMatchOf Context triple: [MLS Cup 2000, isFinalMatchOf, 2000 MLS season]
-
A.
isFinalEngagementOf
chosen
Indicates that a given engagement is the last or concluding engagement in a sequence or series of engagements involving the same entities.
-
B.
isRematchOfFinal
Indicates that a match is a subsequent encounter replaying the same opponents and stakes as a previous final match.
-
C.
isFinalInstallmentOf
Indicates that one work or item is the concluding or last part in a series, sequence, or collection of related works.
-
D.
finalMatchDate
Indicates the calendar date on which the final or deciding match in a series, tournament, or competition takes place.
-
E.
nextFinals
Indicates that one event, match, or stage directly follows another as the subsequent or upcoming finals in a sequence.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.