Triple
T8289862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aero Shake |
E193866
|
entity |
| Predicate | defaultStateInWindows10 |
P31938
|
FINISHED |
| Object | enabled |
—
|
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: enabled | Statement: [Aero Shake, defaultStateInWindows10, enabled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultStateInWindows10 Context triple: [Aero Shake, defaultStateInWindows10, enabled]
-
A.
statusInWindows10
Indicates the status or condition of something specifically within the context of the Windows 10 operating system.
-
B.
defaultSettingInWindows10
chosen
Indicates that one entity is configured as the default setting within the Windows 10 operating system.
-
C.
statusInWindows8
Indicates the condition or state that something has within the context of the Windows 8 operating system.
-
D.
windows
Indicates that one entity is a window of, or is associated as a window-related component or feature to, another entity.
-
E.
displayState
Indicates the current visual or presentation status of an item, such as whether and how it is shown, hidden, or rendered in a user interface or display context.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c99fdd48190a3f304237be609a0 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.