Triple
T27750267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Help |
E702095
|
entity |
| Predicate | statusInWindowsVista |
P183713
|
FINISHED |
| Object | not installed 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: not installed by default | Statement: [Windows Help, statusInWindowsVista, not installed by default]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInWindowsVista Context triple: [Windows Help, statusInWindowsVista, not installed by default]
-
A.
statusInWindows7
Indicates the status or condition of an entity specifically within the context of the Windows 7 operating system.
-
B.
statusInWindows11
Indicates the status or condition of something specifically within the context of the Windows 11 operating system.
-
C.
statusInWindows10
Indicates the status or condition of something specifically within the context of the Windows 10 operating system.
-
D.
statusInWindows8
Indicates the condition or state that something has within the context of the Windows 8 operating system.
-
E.
defaultStateInWindows7
Indicates that something is in its standard or initial configuration specifically within the Windows 7 operating system.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: April 27, 2026, 4:19 p.m.