Triple
T9761791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSNotificationCenter |
E236686
|
entity |
| Predicate | notificationDelivery |
P10739
|
FINISHED |
| Object | notifications are identified by name (NSString) |
—
|
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: notifications are identified by name (NSString) | Statement: [NSNotificationCenter, notificationDelivery, notifications are identified by name (NSString)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notificationDelivery Context triple: [NSNotificationCenter, notificationDelivery, notifications are identified by name (NSString)]
-
A.
notificationType
Indicates the specific category or kind of notification associated with an event or action.
-
B.
deliveryConfirmation
Indicates that a delivery has been successfully completed and acknowledged, confirming that the intended recipient has received the item or shipment.
-
C.
notificationDeadline
Indicates the time or date by which a required notification must be sent or received.
-
D.
deliveryMode
chosen
Indicates the method or channel through which something (such as a product, service, or information) is delivered or provided.
-
E.
requiresNotification
Indicates that a particular action, event, or state must trigger a notification to be sent to relevant parties.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda04c70108190a8ed09eb6f2a124e |
completed | April 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.