Triple
T11231250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SBC Communications |
E265825
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | SBC |
E265825
|
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: SBC | Statement: [SBC Communications, shortName, SBC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SBC Context triple: [SBC Communications, shortName, SBC]
-
A.
SBC
SBC is a standard Bluetooth audio codec used for wireless transmission of sound between devices such as headphones and smartphones.
-
B.
SBC
SBC is the Indian Railways station code for Krantivira Sangolli Rayanna (Bengaluru) railway station, the main rail hub of Bengaluru, Karnataka.
-
C.
SBC
SBC is an abbreviation commonly used to refer to a Solar Blind Channel, a detection or communication channel operating in a UV wavelength range where solar background radiation is minimal.
-
D.
SBC
SBC is a collegiate athletic conference in the NCAA Division I Football Bowl Subdivision, primarily comprising universities from the southern United States.
-
E.
SBC Communications
chosen
SBC Communications was a major U.S. telecommunications company that grew through acquisitions and later rebranded as AT&T Inc.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9026e1c81909456ac946bbba972 |
completed | April 9, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4ad49b5cc8190b99cb2cd8de72109 |
completed | April 19, 2026, 10:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.