Triple
T17896823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charter Communications, Inc. |
E447450
|
entity |
| Predicate | tickerSymbol |
P1447
|
FINISHED |
| Object | CHTR |
—
|
NE NERFINISHED |
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: CHTR | Statement: [Charter Communications, Inc., tickerSymbol, CHTR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CHTR Context triple: [Charter Communications, Inc., tickerSymbol, CHTR]
-
A.
CHTR
chosen
CHTR is the stock ticker symbol for Charter Communications, a major U.S. telecommunications and cable services provider.
-
B.
CHT
CHT is the National Rail station code for Chertsey railway station in Surrey, England.
-
C.
CHT
CHT is the IATA airport code for Tuuta Airport, which serves the Chatham Islands of New Zealand.
-
D.
CHT
CHT is the commonly used abbreviation for Hong Kong’s Cross-Harbour Tunnel, a major underwater road tunnel linking Hong Kong Island and Kowloon.
-
E.
TCH
TCH was the International Ice Hockey Federation (IIHF) country code used to represent the Czechoslovakia men's national ice hockey team in international competition.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d8045748190a4e8c4684439a96b |
completed | April 19, 2026, 9:16 a.m. |
Created at: April 10, 2026, 10:19 a.m.