Triple
T17189493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BTCL |
E417190
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | BTCL |
E417190
|
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: BTCL | Statement: [BTCL, shortName, BTCL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BTCL Context triple: [BTCL, shortName, BTCL]
-
A.
BTCL
chosen
BTCL (Bangladesh Telecommunications Company Limited) is the state-owned telecommunications operator in Bangladesh, providing fixed-line, broadband, and related communication services nationwide.
-
B.
BTC
BTC is the IATA airport code for Batticaloa Airport in Sri Lanka.
-
C.
BBTC
BBTC is the stock ticker symbol for Bombay Burmah Trading Corporation, a long-established Indian conglomerate involved in plantations, healthcare, auto-ancillaries, and other businesses.
-
D.
BITC
BITC (Burnt-In Timecode) is a visual representation of timecode numbers superimposed directly onto video frames for easy reference during editing and review.
-
E.
ESBTC
ESBTC is the UN/LOCODE identifier for the port and location of Betancuria in Spain.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42d986b60819085c515101cfe65fe |
completed | April 19, 2026, 1:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01674a3a78819094c093daac0e508d |
completed | May 11, 2026, 5:21 a.m. |
Created at: April 10, 2026, 5:37 a.m.