Triple
T7858224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disk Cleanup |
E182429
|
entity |
| Predicate | canBeRunFrom |
P19950
|
FINISHED |
| Object | Start menu |
—
|
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: Start menu | Statement: [Disk Cleanup, canBeRunFrom, Start menu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeRunFrom Context triple: [Disk Cleanup, canBeRunFrom, Start menu]
-
A.
canRunOn
Indicates that one entity is capable of operating, executing, or functioning on another entity (such as a platform, system, or environment).
-
B.
canBeInvokedFrom
chosen
Indicates that one entity (such as a function, method, or component) is able to be called or triggered directly from another specified context or entity.
-
C.
canBeInvokedBy
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
-
D.
canBeDeployedUnder
Indicates that one entity is permitted or suitable to be deployed or operated under the conditions, context, or authority defined by another entity.
-
E.
canBeCalledInto
Indicates that one entity has the authority or ability to summon, request the presence of, or formally convene 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb1a76f8648190976b488d0d8658ef |
completed | March 31, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:52 p.m.