Triple
T28177162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Diego Legion |
E715923
|
entity |
| Predicate | previouslyPlayedHomeMatchesAt |
P8186
|
FINISHED |
| Object | Torero Stadium |
—
|
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: Torero Stadium | Statement: [San Diego Legion, previouslyPlayedHomeMatchesAt, Torero Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyPlayedHomeMatchesAt Context triple: [San Diego Legion, previouslyPlayedHomeMatchesAt, Torero Stadium]
-
A.
playedHomeMatchesIn
chosen
Indicates that an entity (typically a sports team) hosted its home matches at a specified venue or location.
-
B.
playedHomeGamesFrom
Indicates the time period during which a team or player hosted their home games at a particular venue.
-
C.
hostedHomeMatchesFor
Indicates that an entity organized and held competitive matches at its own home venue for another entity or group.
-
D.
playedHomeGamesUntil
Indicates the period up to which a team or player hosted their home games at a particular venue.
-
E.
previousHomeFieldUse
Indicates that one entity was formerly used as the home field or primary venue for another entity before a later change.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 27, 2026, 10:17 p.m.