Triple
T7980504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System Restore |
E185557
|
entity |
| Predicate | canBeStartedFrom |
P50742
|
FINISHED |
| Object | within Windows |
—
|
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: within Windows | Statement: [System Restore, canBeStartedFrom, within Windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeStartedFrom Context triple: [System Restore, canBeStartedFrom, within Windows]
-
A.
canBeActivatedFor
Indicates that one entity is capable of being put into an active or operational state by or for another entity.
-
B.
canBeEstablishedBy
Indicates that a particular state, condition, or relationship is able to be brought into existence or made valid through the actions or intervention of a specified entity.
-
C.
canBeLoadedAt
Indicates that an entity is capable of being placed onto or into another entity (such as a vehicle, container, or system) at a specific location or point in time.
-
D.
canCommence
chosen
Indicates that a particular process, event, or action is allowed or ready to begin under the given conditions.
-
E.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as 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.