Triple
T32536527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Credential Guard |
E831603
|
entity |
| Predicate | storesSecretsIn |
P176369
|
FINISHED |
| Object | isolated virtualized environment |
—
|
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: isolated virtualized environment | Statement: [Credential Guard, storesSecretsIn, isolated virtualized environment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesSecretsIn Context triple: [Credential Guard, storesSecretsIn, isolated virtualized environment]
-
A.
storesInterfaceIn
Indicates that one entity keeps or maintains an interface definition within another entity (such as a container, module, or storage location).
-
B.
storesKeys
Indicates that one entity holds or retains the keys belonging to or used by another entity.
-
C.
storesPasswordAs
Indicates that one entity keeps or maintains another entity’s password in a particular form or location.
-
D.
storageOrgan
Indicates that one entity serves as a storage organ (a specialized structure for storing substances like nutrients or water) for another entity.
-
E.
storedBy
Indicates that one entity is kept, maintained, or held in storage by another entity.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 1:01 a.m.