Triple
T34393785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Telecommunications Limited |
E882775
|
entity |
| Predicate | hasMobileBrand |
P194697
|
FINISHED |
| Object | Singtel Mobile |
—
|
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 Mobile | Statement: [Singapore Telecommunications Limited, hasMobileBrand, Singtel Mobile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMobileBrand Context triple: [Singapore Telecommunications Limited, hasMobileBrand, Singtel Mobile]
-
A.
isMobile
Indicates that an entity is capable of moving or being moved freely rather than remaining fixed in one place.
-
B.
hasNetworkBrand
chosen
Indicates that one entity is associated with or operates under the network brand specified by another entity.
-
C.
hasMobileKey
Indicates that an entity possesses or is associated with a mobile-based digital key used for access or authentication.
-
D.
isMobileBase
Indicates that an entity serves as a movable or mobile base or platform for other entities or operations.
-
E.
hasCellularModel
Indicates that one entity serves as a cellular (cell-based) model or system used to study, represent, or simulate the biological properties or behavior of 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:59 a.m.