Triple
T1033874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jose Earthquakes |
E22314
|
entity |
| Predicate | expansionReturnToMLS |
P18820
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [San Jose Earthquakes, expansionReturnToMLS, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionReturnToMLS Context triple: [San Jose Earthquakes, expansionReturnToMLS, 2008]
-
A.
joinedMLS
chosen
Indicates that an entity became a member of, or was admitted into, Major League Soccer (MLS).
-
B.
expansionFromPreviousSeason
Indicates that the current season represents an expansion or enlargement relative to the immediately preceding season.
-
C.
leagueExpansionRelatedTo
Indicates a relationship where one league’s expansion, growth, or addition of teams is connected or relevant to another entity, event, or change.
-
D.
expansionFranchiseWith
Indicates a relationship where one entity is an expansion franchise that is formally associated with, derived from, or added to another existing entity (such as a league, organization, or parent franchise).
-
E.
movedToLeague
Indicates that an entity changed affiliation or membership from one league to another.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8d669448190955507e2e4975b9f |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b728ad3481909cf1430349cb9bba |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.