Triple
T355716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2007 |
E7537
|
entity |
| Predicate | New England Revolution MLS Cup finals lost |
P7498
|
FINISHED |
| Object | 3rd consecutive |
—
|
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: 3rd consecutive | Statement: [MLS Cup 2007, New England Revolution MLS Cup finals lost, 3rd consecutive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: New England Revolution MLS Cup finals lost Context triple: [MLS Cup 2007, New England Revolution MLS Cup finals lost, 3rd consecutive]
-
A.
losingTeamFinalAppearancesCountForNewEnglandRevolution
chosen
Indicates the number of times the New England Revolution appeared in a final and ended up as the losing team.
-
B.
finalsLosingTeam
Indicates the team that was defeated in the final match of a competition or tournament.
-
C.
NewEnglandRevolutionCoach
Indicates that one entity serves as the head coach of the New England Revolution soccer team.
-
D.
penaltyShootoutLoser
Indicates the team or player that loses a match as a result of a penalty shootout.
-
E.
managerOfLosingTeam
Indicates that the subject is the manager of a team that lost a particular game, match, or competition.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebad8bf08190b4a38ffd9157d641 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e9589e7c8190b2d3af8f858c96af |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.