Triple
T7980491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System Restore |
E185557
|
entity |
| Predicate | automaticTriggerEvent |
P693
|
FINISHED |
| Object | system changes |
—
|
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 changes | Statement: [System Restore, automaticTriggerEvent, system changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: automaticTriggerEvent Context triple: [System Restore, automaticTriggerEvent, system changes]
-
A.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
B.
usesTriggerSystem
Indicates that one entity operates or functions by means of a trigger-based mechanism or system provided or associated with another entity.
-
C.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
-
D.
triggered
chosen
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
E.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c274ce48190854d389d43ce14b8 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.