Triple
T3157524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mavs Gaming |
E66019
|
entity |
| Predicate | hasHashtag |
P2920
|
FINISHED |
| Object | #MavsGG |
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: #MavsGG | Statement: [Mavs Gaming, hasHashtag, #MavsGG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: #MavsGG Context triple: [Mavs Gaming, hasHashtag, #MavsGG]
-
A.
Mavs Gaming Hub
Mavs Gaming Hub is a dedicated esports facility and training center for the Dallas Mavericks’ NBA 2K League team, Mavs Gaming.
-
B.
Houston Mavericks
The Houston Mavericks were a professional basketball team based in Houston, Texas, that competed in the original American Basketball Association during the late 1960s.
-
C.
Mavs Gaming
chosen
Mavs Gaming is the official NBA 2K League esports team affiliated with the Dallas Mavericks organization.
-
D.
Omaha Mavericks
The Omaha Mavericks are the athletic teams representing the University of Nebraska Omaha in NCAA Division I sports.
-
E.
Dallas Mavericks
The Dallas Mavericks are a professional NBA basketball team based in Dallas, Texas.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5ec0da88190a83f3448ac76e98e |
completed | March 8, 2026, 4:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b235c3554c8190a94040955391a020 |
completed | March 12, 2026, 3:40 a.m. |
Created at: March 8, 2026, 3:05 p.m.