Triple
T8220600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ReadyBoost |
E192047
|
entity |
| Predicate | canBeEnabledBy |
P28803
|
FINISHED |
| Object | user |
—
|
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: user | Statement: [ReadyBoost, canBeEnabledBy, user]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeEnabledBy Context triple: [ReadyBoost, canBeEnabledBy, user]
-
A.
enabledBy
Indicates that one entity functions as the cause, condition, or resource that makes it possible for another entity’s action, state, or capability to occur or be realized.
-
B.
canBeActivatedFor
chosen
Indicates that one entity is capable of being put into an active or operational state by or for another entity.
-
C.
canBeDisabledOn
Indicates that a feature, function, or capability has the property that it can be turned off or deactivated when applied to the referenced entity.
-
D.
canBeInvokedBy
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
-
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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb77c782a8819086019ab6bac05749 |
completed | March 31, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:45 p.m.