Triple
T13961779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacramento Kings practice facility |
E335811
|
entity |
| Predicate | tenant |
P75
|
FINISHED |
| Object | Kings Guard Gaming |
E67180
|
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: Kings Guard Gaming | Statement: [Sacramento Kings practice facility, tenant, Kings Guard Gaming]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kings Guard Gaming Context triple: [Sacramento Kings practice facility, tenant, Kings Guard Gaming]
-
A.
Kings Guard Gaming
chosen
Kings Guard Gaming is the NBA 2K League esports team affiliated with the Sacramento Kings organization.
-
B.
Bucks Gaming
Bucks Gaming is the Milwaukee Bucks’ official esports team that competes in the NBA 2K League.
-
C.
Grizz Gaming
Grizz Gaming is the official NBA 2K League esports team affiliated with the Memphis Grizzlies.
-
D.
Pacers Gaming
Pacers Gaming is the official NBA 2K League esports team affiliated with the Indiana Pacers organization.
-
E.
T-Wolves Gaming
T-Wolves Gaming is the official NBA 2K League esports team affiliated with the NBA's Minnesota Timberwolves.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7c73d48190b8e02971b5a8ed5f |
completed | April 14, 2026, 12:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbac8e47d48190a1d5e841810fe50c |
completed | May 6, 2026, 9:03 p.m. |
Created at: April 9, 2026, 10:18 p.m.