Triple
T22379185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guam Administrative Adjudication procedures |
E553225
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative law framework |
C11529
|
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 law framework Context triple: [Guam Administrative Adjudication procedures, instanceOf, administrative law framework]
-
A.
branch of administrative law
A branch of administrative law is a specialized area within the broader field that governs the organization, powers, procedures, and accountability of public administrative agencies in a particular domain (such as environmental regulation, immigration, or social welfare).
-
B.
administrative law case
An administrative law case is a legal dispute that arises from actions or decisions of government agencies, focusing on the interpretation, application, or validity of administrative rules and procedures.
-
C.
legal-political framework
A legal-political framework is the structured system of laws, institutions, and governing principles that defines how power is distributed, exercised, and constrained within a society.
-
D.
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.
-
E.
regulatory framework
chosen
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.