Triple
T20610562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StreetPass |
E506435
|
entity |
| Predicate | notification |
P140749
|
FINISHED |
| Object | system notifies user when StreetPass data is received |
—
|
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: system notifies user when StreetPass data is received | Statement: [StreetPass, notification, system notifies user when StreetPass data is received]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notification Context triple: [StreetPass, notification, system notifies user when StreetPass data is received]
-
A.
notificationType
Indicates the specific category or kind of notification associated with an event or action.
-
B.
requiresNotification
Indicates that a particular action, event, or state must trigger a notification to be sent to relevant parties.
-
C.
notificationDeadline
Indicates the time or date by which a required notification must be sent or received.
-
D.
announcementFormula
Indicates that one entity is the formal content or wording used in an announcement made by another entity.
-
E.
noticeRequirement
Indicates that one party is obligated to provide advance notification to another party before a specified action, change, or event occurs.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad6f53481908fb242947dda7028 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:41 a.m.