Triple
T3146486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celtics Crossover Gaming |
E65775
|
entity |
| Predicate | hasRival |
P1375
|
FINISHED |
| Object | Knicks Gaming |
E65774
|
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: Knicks Gaming | Statement: [Celtics Crossover Gaming, hasRival, Knicks Gaming]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Knicks Gaming Context triple: [Celtics Crossover Gaming, hasRival, Knicks Gaming]
-
A.
Knicks Gaming
chosen
Knicks Gaming is the official NBA 2K League esports team affiliated with the New York Knicks.
-
B.
Nets Gaming Crew
Nets Gaming Crew is a professional NBA 2K League esports team affiliated with the Brooklyn Nets.
-
C.
Pacers Gaming
Pacers Gaming is the official NBA 2K League esports team affiliated with the Indiana Pacers organization.
-
D.
Bucks Gaming
Bucks Gaming is the Milwaukee Bucks’ official esports team that competes in the NBA 2K League.
-
E.
Mavs Gaming
Mavs Gaming is the official NBA 2K League esports team affiliated with the Dallas Mavericks organization.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada598ccf08190b8817c456f38f2d7 |
completed | March 8, 2026, 4:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b235bad36c8190ab93312950380d36 |
completed | March 12, 2026, 3:40 a.m. |
Created at: March 8, 2026, 3:05 p.m.