Triple
T25257038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USSD |
E633197
|
entity |
| Predicate | advantageOverSMS |
P158433
|
FINISHED |
| Object | no message storage |
—
|
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: no message storage | Statement: [USSD, advantageOverSMS, no message storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advantageOverSMS Context triple: [USSD, advantageOverSMS, no message storage]
-
A.
supportsSMS
Indicates that one entity provides the capability for another entity to send, receive, or otherwise use SMS (Short Message Service) messaging.
-
B.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
C.
hasMessagingFeatures
Indicates that an entity provides or supports messaging-related capabilities or functions.
-
D.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
E.
communicationService
Indicates a relationship where one entity provides or facilitates a means for another entity to exchange information or messages.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4838f46e88190874064d73ab69ce3 |
completed | May 1, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:13 p.m.