Triple
T27885819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Service account |
E705218
|
entity |
| Predicate | logonName |
P163750
|
FINISHED |
| Object | NT AUTHORITY\NETWORK SERVICE |
—
|
NE NERFINISHED |
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: NT AUTHORITY\NETWORK SERVICE | Statement: [Network Service account, logonName, NT AUTHORITY\NETWORK SERVICE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logonName Context triple: [Network Service account, logonName, NT AUTHORITY\NETWORK SERVICE]
-
A.
logonType
Indicates the manner or method by which a user or entity authenticates and establishes a login session.
-
B.
credentialName
Indicates the specific title or label assigned to a credential associated with an entity.
-
C.
displayName
Indicates the human-readable name or label that is shown to users when presenting an entity.
-
D.
anonymousLoginUsername
Indicates that a username is used specifically for logging in anonymously, without revealing the user's real identity.
-
E.
commonName
Indicates that one entity is the commonly used or vernacular name by which the other entity is known.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 6:33 p.m.