Triple
T8175464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Security Center |
E190927
|
entity |
| Predicate | notifiesUserWhen |
P41194
|
FINISHED |
| Object | firewall is turned off |
—
|
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: firewall is turned off | Statement: [Security Center, notifiesUserWhen, firewall is turned off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notifiesUserWhen Context triple: [Security Center, notifiesUserWhen, firewall is turned off]
-
A.
requiresNotification
chosen
Indicates that a particular action, event, or state must trigger a notification to be sent to relevant parties.
-
B.
requiresNotificationTo
Indicates that one entity must send a notification to another entity before or when a certain condition, event, or action occurs.
-
C.
requiresNotificationFrom
Indicates that one entity must receive a notification from another entity before or when a certain condition, event, or action occurs.
-
D.
notificationType
Indicates the specific category or kind of notification associated with an event or action.
-
E.
requiresNoticeContent
Indicates that one party must provide specific informational content in a notice as a condition or requirement for the related action or relationship.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4ab8295081909a450fcaa34f6ec6 |
completed | March 31, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.