Triple
T27926687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS10-042 |
E707854
|
entity |
| Predicate | userRightsImpact |
P37632
|
FINISHED |
| Object | depends on privileges of logged-on user |
—
|
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: depends on privileges of logged-on user | Statement: [MS10-042, userRightsImpact, depends on privileges of logged-on user]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userRightsImpact Context triple: [MS10-042, userRightsImpact, depends on privileges of logged-on user]
-
A.
humanAccessLevel
Indicates the level or degree of access or permissions granted to a human within a system or context.
-
B.
sharesUSRightsWith
Indicates that one entity holds and grants to another entity shared rights or interests specifically related to the United States.
-
C.
hasRightsOver
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
-
D.
accessRole
chosen
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
-
E.
hasRightsStatus
Indicates that an entity is associated with a particular legal or usage rights condition or status.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
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, 7 p.m.