Triple
T31582843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows NT security model |
E805871
|
entity |
| Predicate | supportsSecurityPrincipal |
P180592
|
FINISHED |
| Object | user account |
—
|
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: user account | Statement: [Windows NT security model, supportsSecurityPrincipal, user account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSecurityPrincipal Context triple: [Windows NT security model, supportsSecurityPrincipal, user account]
-
A.
hasSecuritySupport
Indicates that one entity provides security-related assistance, maintenance, or protection services for another entity.
-
B.
canUseSecurity
Indicates that one entity is permitted or able to employ or access a specified security mechanism, feature, or resource.
-
C.
hasSecurityAuthority
chosen
Indicates that one entity possesses the right or power to enforce, manage, or make decisions about security over another entity or resource.
-
D.
isSecurityFor
Indicates that one entity serves as protection, safeguard, or collateral guaranteeing the obligations, value, or safety of another entity.
-
E.
hasPrincipalProtection
Indicates that an investment or financial product guarantees the return of the original principal amount, protecting it from loss.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:24 p.m.