Triple
T5304008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jose Earthquakes |
E120050
|
entity |
| Predicate | relocatedFranchiseYear |
P46928
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [San Jose Earthquakes, relocatedFranchiseYear, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocatedFranchiseYear Context triple: [San Jose Earthquakes, relocatedFranchiseYear, 2005]
-
A.
foundedAsFranchiseYear
Indicates the year in which an entity was established specifically as a franchise.
-
B.
team2RelocationYear
chosen
Indicates the year in which the second team in a relationship was relocated to a different place or franchise.
-
C.
winningFranchiseLaterRelocatedTo
Indicates that the franchise which won (e.g., a championship or title) subsequently moved its location to a different city or region.
-
D.
appliedToFranchiseFoundedIn
Indicates that something (such as a rule, policy, or action) is applied specifically to a franchise that was founded in a particular time or place.
-
E.
establishedAsCurrentFranchise
Indicates that an entity has been formally designated or recognized as the current active franchise for another entity.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.