Triple
T32518097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NomCom Operating Procedures |
E831110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | operating procedures |
C53016
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: operating procedures Context triple: [NomCom Operating Procedures, instanceOf, operating procedures]
-
A.
rules of procedure
Rules of procedure are formal guidelines that govern how decisions are proposed, discussed, and made within an organization, assembly, or legal process.
-
B.
governmental procedure
A governmental procedure is a formally established sequence of actions, rules, and decision-making steps that public authorities follow to create, implement, or enforce laws and policies.
-
C.
communications procedure
A communications procedure is a defined sequence of steps and rules that govern how information is created, transmitted, received, and responded to between parties or systems.
-
D.
logistical operation
A logistical operation is a coordinated set of activities and processes that plan, implement, and control the efficient movement and storage of goods, information, or resources from origin to destination.
-
E.
organizational process
chosen
An organizational process is a structured set of related activities and workflows that an organization systematically performs to achieve specific goals, deliver value, and ensure consistent, repeatable outcomes.
- F. None of above.
Provenance (1 batch)
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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.