Triple
T14898724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Journal of Environmental and Administrative Law |
E359945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative law journal |
C3986
|
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 journal Context triple: [Michigan Journal of Environmental and Administrative Law, instanceOf, administrative law journal]
-
A.
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.
-
B.
administrative law scholar
An administrative law scholar is a legal expert who studies, analyzes, and critiques the structures, procedures, and decisions of administrative agencies and their role in governance.
-
C.
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).
-
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.
law journal
chosen
A law journal is a periodical publication, typically produced by law schools or legal organizations, that features scholarly articles, case notes, and commentary on legal issues and developments.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 2:11 a.m.