Triple
T8022281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Management Console 2.0 |
E186765
|
entity |
| Predicate | userModeVariants |
P11331
|
FINISHED |
| Object | full access |
—
|
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: full access | Statement: [Microsoft Management Console 2.0, userModeVariants, full access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userModeVariants Context triple: [Microsoft Management Console 2.0, userModeVariants, full access]
-
A.
usedOnMode
chosen
Indicates that something is applied, operated, or functions specifically in a given mode or operational setting.
-
B.
modeType
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
-
C.
modeBDescription
Indicates the descriptive label or explanation associated with a specific operational or behavioral mode B.
-
D.
alternateMode
Indicates that one entity functions as an alternative form, configuration, or mode of operation for another entity.
-
E.
modeADescription
Indicates the descriptive text or explanation associated with a particular mode of operation or state.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8eab9c81908098e6b17957316c |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.