Triple
T3306063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Diego Loyal SC |
E69451
|
entity |
| Predicate | inauguralSeasonLeague |
P43853
|
FINISHED |
| Object | USL Championship 2020 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: USL Championship 2020 season | Statement: [San Diego Loyal SC, inauguralSeasonLeague, USL Championship 2020 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inauguralSeasonLeague Context triple: [San Diego Loyal SC, inauguralSeasonLeague, USL Championship 2020 season]
-
A.
inauguralSeason
Indicates the first season in which an entity (such as a team, league, or event) officially began participating or operating.
-
B.
leagueFoundedSeason
Indicates the season during which a particular league was established or founded.
-
C.
openingSeason
Indicates that an entity marks the beginning or first season of another entity, such as a series, event, or competition.
-
D.
homeLeagueSeasonStart
Indicates the league season in which an entity begins playing its home games.
-
E.
beganInLeagueSeason
chosen
Indicates that an entity (such as a team, player, or competition) began its participation or activity during a specified league season.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c9470881908c36c1984fdbb67b |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.