Triple
T31674549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jose Grizzlies |
E808362
|
entity |
| Predicate | homeArenaCurrentName |
P172879
|
FINISHED |
| Object | SAP Center at San Jose |
—
|
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: SAP Center at San Jose | Statement: [San Jose Grizzlies, homeArenaCurrentName, SAP Center at San Jose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeArenaCurrentName Context triple: [San Jose Grizzlies, homeArenaCurrentName, SAP Center at San Jose]
-
A.
homeArenaAlternateName
Indicates that an entity’s home arena is known by an alternate or secondary name.
-
B.
homeArenaOfChampionTeam
Indicates that a particular arena serves as the primary home venue for a specified champion team.
-
C.
homeArenaNickname
Indicates the commonly used or informal nickname of a team's or organization's home arena.
-
D.
homeArenaNameSponsor
Indicates that an entity’s home arena has a specific corporate or branded sponsor name.
-
E.
hostStadiumCurrentName
Indicates that a stadium is the current venue where an event or team is hosted under its present official name.
- F. None of above. chosen
Provenance (4 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 11:02 p.m.