Triple
T31674489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 MLS SuperDraft |
E808360
|
entity |
| Predicate | expansionTeamParticipating |
P20787
|
FINISHED |
| Object | Real Salt Lake |
—
|
NE NERFINISHED |
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: Real Salt Lake | Statement: [2005 MLS SuperDraft, expansionTeamParticipating, Real Salt Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionTeamParticipating Context triple: [2005 MLS SuperDraft, expansionTeamParticipating, Real Salt Lake]
-
A.
expansionTeamIn
Indicates that a sports team entered a league or competition as an expansion team in a specified season, year, or context.
-
B.
expansionTeamWith
chosen
Indicates that one entity is an expansion team associated with, or added to, another entity such as a league, division, or organization.
-
C.
expandedFromTeams
Indicates that something has been enlarged, extended, or developed starting from one or more teams as the original basis.
-
D.
expansionTeamNote
Indicates that there is a note or annotation specifically about an expansion team associated with the related entities.
-
E.
expansionTeamAddedYear
Indicates the year in which an expansion team was officially added to a league or organization.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 30, 2026, 11:02 p.m.