Triple
T712244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Administrative Rules |
E14235
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | compilation of regulations |
C4383
|
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: compilation of regulations Context triple: [Oregon Administrative Rules, instanceOf, compilation of regulations]
-
A.
statutory compilation
A statutory compilation is an organized collection of statutes, often arranged by subject or jurisdiction, that consolidates and presents the text of enacted laws in a systematic, accessible format.
-
B.
compilation of oral law
A compilation of oral law is an organized written collection of previously unwritten legal traditions, interpretations, and rulings that were transmitted orally within a community or religious-legal system.
-
C.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
D.
United States Army regulation
A United States Army regulation is an official, binding directive issued by the Department of the Army that prescribes policies, responsibilities, and procedures governing the organization, operations, and conduct of Army personnel and activities.
-
E.
formal rules
chosen
Formal rules are explicitly defined, codified guidelines or principles that govern behavior, procedures, or decision-making within a specific system or organization.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:36 p.m.