Triple
T28023553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group Policy Management Console |
E707750
|
entity |
| Predicate | managesScope |
P127594
|
FINISHED |
| Object | sites |
—
|
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: sites | Statement: [Group Policy Management Console, managesScope, sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesScope Context triple: [Group Policy Management Console, managesScope, sites]
-
A.
modificationScope
Indicates the extent or range within which a change, adjustment, or alteration applies to an entity or its attributes.
-
B.
definesScopeFor
Indicates that one entity establishes or delimits the scope, boundaries, or applicability within which another entity operates or is interpreted.
-
C.
scopeOfControl
Indicates the extent or range within which an entity has authority, influence, or control over another entity or set of entities.
-
D.
managingFor
chosen
Indicates that one entity is responsible for directing, supervising, or overseeing activities, resources, or operations on behalf of another entity.
-
E.
syncScope
Indicates that two or more processes, threads, or operations are coordinated to occur within the same synchronization context or boundary.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 8:11 p.m.