Triple
T36981100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2001 Western Conference Semifinals |
E914829
|
entity |
| Predicate | locationOfHomeGamesForSacramentoKings |
P205675
|
FINISHED |
| Object | ARCO Arena |
E109140
|
NE 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: ARCO Arena | Statement: [2001 Western Conference Semifinals, locationOfHomeGamesForSacramentoKings, ARCO Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfHomeGamesForSacramentoKings Context triple: [2001 Western Conference Semifinals, locationOfHomeGamesForSacramentoKings, ARCO Arena]
-
A.
locationForLakersHomeGames
Indicates the venue or place where the Los Angeles Lakers play their home games.
-
B.
LakersHomeArena
Indicates that a given arena serves as the home venue for the Los Angeles Lakers basketball team.
-
C.
primaryBasketballArenaLocation
Indicates the main geographic location where a basketball team’s primary home arena is situated.
-
D.
LosAngelesKingsCity
Indicates that the specified city is the home city or location associated with the Los Angeles Kings.
-
E.
cityOfOregonStateHomeGames
Indicates that the referenced city is the location where the Oregon State team plays its home games.
- F. None of above. chosen
Provenance (5 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efdac1674819093c1039925982625 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.