Triple
T1332004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup trophy |
E28662
|
entity |
| Predicate | originalRetainedByLeague |
P27328
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MLS Cup trophy, originalRetainedByLeague, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRetainedByLeague Context triple: [MLS Cup trophy, originalRetainedByLeague, yes]
-
A.
originalLeague
Indicates the league or competition in which an entity (such as a team or club) initially participated or was first a member.
-
B.
originLeague
Indicates the sports league or competition from which an entity (such as a team, player, or event) originally comes or is associated.
-
C.
formerLeague
Indicates that an entity previously belonged to or participated in a particular league but is no longer a member.
-
D.
managedLeague
Indicates that one entity was responsible for organizing, directing, or overseeing the operations of a particular league.
-
E.
playedInLeagueThatBecame
Indicates that an entity participated in a sports league which later transformed into, merged into, or was rebranded as another specified league.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c5f86c819098e98b046968954a |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0b1326081909aa6beec0cfe8d6c |
completed | March 1, 2026, 10:41 p.m. |
Created at: March 1, 2026, 7:55 p.m.