Triple
T17189484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangladesh Telecommunications Company Limited |
E417189
|
entity |
| Predicate | telecomStandard |
P29523
|
FINISHED |
| Object | PSTN |
—
|
LITERAL 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: PSTN | Statement: [Bangladesh Telecommunications Company Limited, telecomStandard, PSTN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telecomStandard Context triple: [Bangladesh Telecommunications Company Limited, telecomStandard, PSTN]
-
A.
telecommunicationsType
Indicates the specific category or mode of telecommunications service or technology associated with an entity.
-
B.
telephoneStandard
chosen
Indicates that there is a relationship involving the use of a particular telephone standard or protocol for communication between entities.
-
C.
telecomRegime
Indicates a regulatory or governance framework that defines how telecommunications services are organized, controlled, and operated within a given context.
-
D.
telecommunicationSystem
Indicates a relationship where communication between entities is carried out over a distance using electronic or digital transmission systems.
-
E.
telecommunicationsProvider
Indicates that one entity provides telecommunications services (such as phone, internet, or data connectivity) to another entity.
- F. None of above.
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. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.