Triple
T27885799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Service account |
E705218
|
entity |
| Predicate | privilegeLevel |
P69042
|
FINISHED |
| Object | higher than Local Service 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: higher than Local Service account | Statement: [Network Service account, privilegeLevel, higher than Local Service account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privilegeLevel Context triple: [Network Service account, privilegeLevel, higher than Local Service account]
-
A.
authorizationLevel
chosen
Indicates the degree or tier of access rights or permissions granted to an entity within a system or context.
-
B.
holderPrivileges
Indicates that one entity possesses specific rights, permissions, or advantages granted to the holder of another entity.
-
C.
humanAccessLevel
Indicates the level or degree of access or permissions granted to a human within a system or context.
-
D.
formerPrivilege
Indicates that an entity once held a certain privilege or right but no longer does so in the present.
-
E.
requiresPrivileges
Indicates that performing the referenced action or accessing the referenced resource is contingent on the actor having specific privileges or permissions.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:33 p.m.