Triple
T7980484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System Restore |
E185557
|
entity |
| Predicate | restorePointType |
P33684
|
FINISHED |
| Object | system state snapshot |
—
|
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 state snapshot | Statement: [System Restore, restorePointType, system state snapshot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restorePointType Context triple: [System Restore, restorePointType, system state snapshot]
-
A.
restorationType
Indicates the specific kind or category of restoration applied to an entity, such as the method, scope, or approach used to return it to a prior or improved state.
-
B.
snapshotType
chosen
Indicates the specific kind or category of snapshot associated with an entity or event.
-
C.
restorationGoal
Indicates that an action or plan is intended to return something to a previous, original, or improved state or condition.
-
D.
resetType
Indicates the specific kind or method of reset applied to an entity, process, or system state.
-
E.
restoredBy
Indicates that an entity has been returned to a previous or improved state through the actions or intervention of another entity.
- 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.