Triple
T31459672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2025 Major League Soccer season |
E802552
|
entity |
| Predicate | hasExpansionTeam |
P20787
|
FINISHED |
| Object | San Diego FC |
—
|
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: San Diego FC | Statement: [2025 Major League Soccer season, hasExpansionTeam, San Diego FC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpansionTeam Context triple: [2025 Major League Soccer season, hasExpansionTeam, San Diego FC]
-
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.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
D.
expandedFromTeams
Indicates that something has been enlarged, extended, or developed starting from one or more teams as the original basis.
-
E.
foundedAsExpansionTeamOf
Indicates that an organization or team was originally established as a new expansion unit of another existing organization or league.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 30, 2026, 9:19 p.m.