Triple
T27885833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Service account |
E705218
|
entity |
| Predicate | networkIdentity |
P166858
|
FINISHED |
| Object | computer account in Active Directory |
—
|
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: computer account in Active Directory | Statement: [Network Service account, networkIdentity, computer account in Active Directory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkIdentity Context triple: [Network Service account, networkIdentity, computer account in Active Directory]
-
A.
localIdentity
Indicates that an entity’s identity or role is defined specifically within a particular local context, scope, or environment, rather than globally.
-
B.
globalIdentity
Indicates that two or more identifiers or representations actually refer to the same underlying global entity or individual.
-
C.
networkOwner
Indicates that one entity holds ownership or primary control over a particular network.
-
D.
publicIdentity
Indicates that an entity’s outward-facing identity or persona is known, presented, or recognized in a public context.
-
E.
currentIdentity
Indicates that an entity’s present or active identity is the one specified in the relationship.
- 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_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 27, 2026, 6:33 p.m.