Triple
T9963332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Security app |
E195619
|
entity |
| Predicate | showsStatusFor |
P45152
|
FINISHED |
| Object | virus and threat protection |
—
|
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: virus and threat protection | Statement: [Windows Security app, showsStatusFor, virus and threat protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsStatusFor Context triple: [Windows Security app, showsStatusFor, virus and threat protection]
-
A.
seeStatus
Indicates that one entity observes or becomes aware of the current state or condition of another entity or process.
-
B.
displayState
chosen
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.
-
C.
exhibitStatus
Indicates the current state or condition of an exhibit within a display, collection, or presentation context.
-
D.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
E.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb718cd588190a4aac48220deddec |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.