Triple
T7144886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary’s Order of the U.S. Department of the Interior |
E166537
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative directive |
C10533
|
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: administrative directive Context triple: [Secretary’s Order of the U.S. Department of the Interior, instanceOf, administrative directive]
-
A.
administrative instrument
chosen
An administrative instrument is a formal tool, document, or mechanism used by an organization or authority to implement, manage, or regulate administrative processes and decisions.
-
B.
administrative authority
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
-
C.
executive order
An executive order is a formal directive issued by a head of the executive branch, such as a president or governor, that manages operations of the government and has the force of law within the scope of existing statutory or constitutional authority.
-
D.
administrative obligation
An administrative obligation is a duty imposed on individuals or organizations to complete specific formal procedures, filings, or compliance tasks required by governing authorities or institutional rules.
-
E.
administrative function
An administrative function is a conceptual class representing tasks and processes that support the organization, coordination, and control of operations within an institution or system.
- 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:46 p.m.