Triple
T32377451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wuauserv |
E827327
|
entity |
| Predicate | recommendedState |
P175828
|
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: [wuauserv, recommendedState, enabled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedState Context triple: [wuauserv, recommendedState, enabled]
-
A.
recommendedMode
Indicates that one entity is suggested or advised as the preferred mode, method, or way of doing or experiencing something in relation to another entity.
-
B.
standardState
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
-
C.
recommendedPolicy
Indicates that one entity suggests or endorses a particular policy for another entity or situation.
-
D.
commendedFor
Indicates that one entity has expressed praise or approval toward another entity specifically because of a particular action, quality, or achievement.
-
E.
principalState
Indicates that an entity serves as the primary or main state associated with another entity or context.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: May 1, 2026, 12:51 a.m.