Triple
T1719336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Firewall |
E37355
|
entity |
| Predicate | defaultState |
P19731
|
FINISHED |
| Object | enabled on supported Windows versions |
—
|
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 on supported Windows versions | Statement: [Windows Firewall, defaultState, enabled on supported Windows versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultState Context triple: [Windows Firewall, defaultState, enabled on supported Windows versions]
-
A.
standardState
chosen
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
-
B.
formerState
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
-
C.
inState
Indicates that an entity is currently located within or belongs to a particular state or condition.
-
D.
stateRock
Indicates that an entity is in a solid, rock-like physical state or condition.
-
E.
secondaryState
Indicates that an entity is in a subordinate or less primary condition, status, or mode relative to its main or primary state.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.