Triple

T34393786
Position Surface form Disambiguated ID Type / Status
Subject Singapore Telecommunications Limited E882775 entity
Predicate hasBroadbandBrand P185254 FINISHED
Object Singtel Fibre Broadband 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: Singtel Fibre Broadband | Statement: [Singapore Telecommunications Limited, hasBroadbandBrand, Singtel Fibre Broadband]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBroadbandBrand
Context triple: [Singapore Telecommunications Limited, hasBroadbandBrand, Singtel Fibre Broadband]
  • A. hasMVNO
    Indicates that one entity operates as a Mobile Virtual Network Operator (MVNO) using the network infrastructure or services provided by another entity.
  • B. hasISP
    Indicates that an entity is subscribed to or uses a particular Internet Service Provider.
  • C. hasBrandType
    Indicates that an entity is associated with or categorized under a particular brand type or classification.
  • D. hasSuburbanServiceBrand
    Indicates that an entity operates or is associated with a specific brand used for its suburban transport services.
  • E. wirelessOperator
    Indicates that an entity operates, manages, or provides services for a wireless communication system or network for another entity.
  • F. None of above. chosen

Provenance (4 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_69f349c1304081909331872829e38106 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7bbf906d8819099020e548dd56bc9 completed May 3, 2026, 9:19 p.m.
PD Predicate disambiguation batch_69f7b9a2dcf88190a7c9e109e41267be completed May 3, 2026, 9:09 p.m.
PDg Predicate description generation batch_69f7bbf812cc8190a16917c5daaff2df completed May 3, 2026, 9:19 p.m.
Created at: May 1, 2026, 1:59 a.m.