Triple
T34393787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Telecommunications Limited |
E882775
|
entity |
| Predicate | hasPayTVBrand |
P200305
|
FINISHED |
| Object | Singtel TV |
—
|
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 TV | Statement: [Singapore Telecommunications Limited, hasPayTVBrand, Singtel TV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPayTVBrand Context triple: [Singapore Telecommunications Limited, hasPayTVBrand, Singtel TV]
-
A.
hasTelevisionChannelBrand
Indicates that an entity is associated with or operates under a particular television channel brand.
-
B.
hasEntertainmentBrand
Indicates that one entity owns, operates, or is formally associated with an entertainment-related brand or franchise.
-
C.
televisionShowBrand
Indicates that a brand is associated with, sponsors, or is featured within a particular television show.
-
D.
hasBroadbandBrand
Indicates that an entity is associated with or marketed under a particular broadband service brand.
-
E.
hasNetworkBrand
Indicates that one entity is associated with or operates under the network brand specified by 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_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69ff7fc715208190a8e4e2cc5aa72d2c |
completed | May 9, 2026, 6:41 p.m. |
Created at: May 1, 2026, 1:59 a.m.