Triple
T21192223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMSC |
E522239
|
entity |
| Predicate | storesMessagesWhen |
P143497
|
FINISHED |
| Object | recipient is unavailable |
—
|
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: recipient is unavailable | Statement: [SMSC, storesMessagesWhen, recipient is unavailable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesMessagesWhen Context triple: [SMSC, storesMessagesWhen, recipient is unavailable]
-
A.
storesInterfaceIn
Indicates that one entity keeps or maintains an interface definition within another entity (such as a container, module, or storage location).
-
B.
sentMessengersTo
Indicates that one entity dispatched or directed messengers to another entity or location for communication or representation.
-
C.
typicallyDeletesMessagesFrom
Indicates that one entity habitually or by default removes or erases messages originating from another entity.
-
D.
storesPackageStatusIn
Indicates that an entity records or maintains the status information of a package within a particular storage location or system.
-
E.
sends
Indicates that one entity transmits or dispatches something (such as a message, object, or signal) to 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733381f288190b3da795f62a39568 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5fa92a2448190896c022dd27511ad |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 16, 2026, 3:07 p.m.