Triple
T7913043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buck Shaw Stadium |
E183745
|
entity |
| Predicate | servedAsHomeStadiumFor |
P2696
|
FINISHED |
| Object | San Jose Earthquakes from 2008 to 2014 |
—
|
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: San Jose Earthquakes from 2008 to 2014 | Statement: [Buck Shaw Stadium, servedAsHomeStadiumFor, San Jose Earthquakes from 2008 to 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsHomeStadiumFor Context triple: [Buck Shaw Stadium, servedAsHomeStadiumFor, San Jose Earthquakes from 2008 to 2014]
-
A.
playedAtStadium
Indicates that an event or game took place at, or was hosted in, a specific stadium.
-
B.
sharesStadiumWith
Indicates that two teams or organizations use the same stadium as their home or primary venue.
-
C.
stadiumFor
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
-
D.
locatedInStadium
Indicates that an entity is situated within or at the premises of a specific stadium.
-
E.
homeStadiumOf
chosen
Indicates that a particular stadium serves as the primary home venue for a specific sports team 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a7383cc819084eab19799209d2e |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:04 p.m.