Triple
T26328726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Administrative Procedure Act hearings |
E662326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative hearing |
C13532
|
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 hearing Context triple: [New York State Administrative Procedure Act hearings, instanceOf, administrative hearing]
-
A.
administrative tribunal
An administrative tribunal is a specialized quasi-judicial body that resolves disputes and makes determinations arising from the decisions or actions of government agencies under specific statutory frameworks.
-
B.
administrative law case
chosen
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.
political status hearing
A political status hearing is a formal legal or governmental proceeding in which the political standing, recognition, or governance arrangements of a territory, group, or entity are reviewed, contested, or clarified.
-
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.
administrative law act
The Administrative Law Act is a legal framework that governs the organization, powers, and procedures of public administrative authorities, as well as the rights and remedies of individuals affected by their decisions.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:32 p.m.