Triple
T13802631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLTX Gaming |
E331677
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | CLTX |
E331676
|
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: CLTX | Statement: [CLTX Gaming, shortName, CLTX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CLTX Context triple: [CLTX Gaming, shortName, CLTX]
-
A.
CLTX
chosen
CLTX is the official NBA 2K League esports team affiliated with the Boston Celtics, competing under the name Celtics Crossover Gaming.
-
B.
LTX
LTX is the IATA airport code for Cotopaxi International Airport serving Latacunga, Ecuador.
-
C.
CLTX Gaming
CLTX Gaming is the official NBA 2K League esports team affiliated with the Boston Celtics organization.
-
D.
TXL
TXL was the IATA airport code for Berlin Tegel Airport, the former main international airport of Berlin, Germany.
-
E.
CLVT
CLVT is the stock ticker symbol for Clarivate Analytics, a global company that provides data, analytics, and insights to support innovation and research across various industries.
- 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_69de025ded6c8190851c108ae559a355 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8da594c81908cb878a8cc1b3a72 |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:12 p.m.