Triple
T8220379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Aero |
E192042
|
entity |
| Predicate | statusInWindows8 |
P81688
|
FINISHED |
| Object | glass transparency removed by default |
—
|
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: glass transparency removed by default | Statement: [Windows Aero, statusInWindows8, glass transparency removed by default]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInWindows8 Context triple: [Windows Aero, statusInWindows8, glass transparency removed by default]
-
A.
statusInWindows10
Indicates the status or condition of something specifically within the context of the Windows 10 operating system.
-
B.
platformStatus
Indicates the current operational or availability state of a platform within a system or service context.
-
C.
windows
Indicates that one entity is a window of, or is associated as a window-related component or feature to, another entity.
-
D.
lastWindowsVersion
Indicates that one entity is the most recent or final version of the Windows operating system associated with another entity.
-
E.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cb4d9b03108190a6785834f21ff75e |
completed | March 31, 2026, 4:29 a.m. |
Created at: March 30, 2026, 5:45 p.m.