Triple
T13815699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mavs Gaming Hub |
E332010
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | Mavs Gaming NBA 2K League team |
E66019
|
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: Mavs Gaming NBA 2K League team | Statement: [Mavs Gaming Hub, usedBy, Mavs Gaming NBA 2K League team]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mavs Gaming NBA 2K League team Context triple: [Mavs Gaming Hub, usedBy, Mavs Gaming NBA 2K League team]
-
A.
Mavs Gaming
chosen
Mavs Gaming is the official NBA 2K League esports team affiliated with the Dallas Mavericks organization.
-
B.
Mavs Gaming Hub
Mavs Gaming Hub is a dedicated esports facility and training center for the Dallas Mavericks’ NBA 2K League team, Mavs Gaming.
-
C.
Knicks Gaming
Knicks Gaming is the official NBA 2K League esports team affiliated with the New York Knicks.
-
D.
Nets Gaming Crew
Nets Gaming Crew is a professional NBA 2K League esports team affiliated with the Brooklyn Nets.
-
E.
Lakers Gaming
Lakers Gaming is the Los Angeles Lakers’ official esports team that competes in the NBA 2K League.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02806e148190996f58934e66d7d8 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8e0112481909deb31f8614f8b93 |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:12 p.m.