Triple
T6089218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial service of the Holy Roman Empire |
E135719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative obligation |
C19905
|
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 obligation Context triple: [Imperial service of the Holy Roman Empire, instanceOf, administrative obligation]
-
A.
federal obligation
A federal obligation is a legally binding duty or commitment imposed or recognized by the national government, typically involving the payment of money, provision of services, or compliance with regulatory requirements.
-
B.
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.
-
C.
administrative instrument
An administrative instrument is a formal tool, document, or mechanism used by an organization or authority to implement, manage, or regulate administrative processes and decisions.
-
D.
administrative function
An administrative function is a conceptual class representing tasks and processes that support the organization, coordination, and control of operations within an institution or system.
-
E.
administrative subpoena
An administrative subpoena is a legal order issued by a government agency, without prior court approval, requiring an individual or entity to provide documents, records, or testimony for an administrative investigation or proceeding.
- F. None of above. chosen
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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:12 p.m.