Triple
T8610229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | verified boot |
E203896
|
entity |
| Predicate | mayStoreKeysIn |
P31950
|
FINISHED |
| Object | hardware-backed keystore |
—
|
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: hardware-backed keystore | Statement: [verified boot, mayStoreKeysIn, hardware-backed keystore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayStoreKeysIn Context triple: [verified boot, mayStoreKeysIn, hardware-backed keystore]
-
A.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
B.
storesKeys
chosen
Indicates that one entity holds or retains the keys belonging to or used by another entity.
-
C.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
D.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
-
E.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ee96ac8190809817c403da2889 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.