Triple
T14060210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pavilion at Pan Am |
E338322
|
entity |
| Predicate | homeTeam |
P2620
|
FINISHED |
| Object | Pacers Gaming |
E67402
|
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: Pacers Gaming | Statement: [The Pavilion at Pan Am, homeTeam, Pacers Gaming]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pacers Gaming Context triple: [The Pavilion at Pan Am, homeTeam, Pacers Gaming]
-
A.
Pacers Gaming
chosen
Pacers Gaming is the official NBA 2K League esports team affiliated with the Indiana Pacers organization.
-
B.
Hawks Talon Gaming Club
Hawks Talon Gaming Club is the official NBA 2K League esports team affiliated with the Atlanta Hawks.
-
C.
Grizz Gaming
Grizz Gaming is the official NBA 2K League esports team affiliated with the Memphis Grizzlies.
-
D.
Bucks Gaming
Bucks Gaming is the Milwaukee Bucks’ official esports team that competes in the NBA 2K League.
-
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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5686f51c81908c33143ecbaae83d |
completed | April 14, 2026, 3 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdefaabd0819098870522a6ce850c |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 10:21 p.m.