Triple
T30747062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covenant of Bahá'u'lláh |
E782841
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | system of administrative authority |
C3212
|
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: system of administrative authority Context triple: [Covenant of Bahá'u'lláh, instanceOf, system of administrative authority]
-
A.
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.
-
B.
system of government agencies
chosen
A system of government agencies is an organized network of public institutions, each with specific legal authority and responsibilities, that collectively implement laws, deliver services, and administer public policy on behalf of the state.
-
C.
public administration
Public administration is the field and practice of implementing government policies, managing public programs, and coordinating resources and personnel to serve the public interest and promote effective governance.
-
D.
royal administration apparatus
The royal administration apparatus is the organized system of offices, officials, and procedures through which a monarchy governs, manages resources, and enforces its authority over a realm.
-
E.
autonomous administrative authority
An autonomous administrative authority is an independent public body, separate from direct government control, empowered to regulate, supervise, or decide specific administrative matters 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:38 p.m.