Triple
T27148523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Administrative Code provisions on historic preservation |
E682318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | body of state administrative regulations |
C31860
|
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: body of state administrative regulations Context triple: [Texas Administrative Code provisions on historic preservation, instanceOf, body of state administrative regulations]
-
A.
regulations
chosen
Regulations are authoritative rules or directives established by a governing body to control, manage, or guide behaviors and processes within a specific domain.
-
B.
body of public law
The body of public law is the collection of legal rules and principles that govern the organization, powers, and functions of the state and its relationship with individuals and other public entities.
-
C.
central government regulations
Central government regulations are legally binding rules and standards issued by national authorities to direct, control, and coordinate activities within a country in accordance with public policy and law.
-
D.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
E.
regulatory provision
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:12 a.m.