Triple
T37825408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniel Horsmanden’s Journal of the Proceedings in The Detection of the Conspiracy |
E943044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | judicial account |
C64398
|
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: judicial account Context triple: [Daniel Horsmanden’s Journal of the Proceedings in The Detection of the Conspiracy, instanceOf, judicial account]
-
A.
judicial office
A judicial office is an official position within the judiciary in which an individual is authorized to interpret and apply the law, preside over legal proceedings, and issue binding decisions.
-
B.
judicial administrative office
A judicial administrative office is an organizational unit within the court system responsible for managing the non-judicial functions of the judiciary, such as case processing, records management, budgeting, staffing, and overall court operations support.
-
C.
court of accounts
A court of accounts is a public institution responsible for auditing government finances, overseeing the legality and efficiency of public spending, and reporting its findings to legislative and executive authorities.
-
D.
judicatory
A judicatory is an official body or assembly within a religious or legal system that has authority to interpret rules, make judgments, and resolve disputes.
-
E.
judicial holding
A judicial holding is the court’s essential legal determination on the specific issues necessary to resolve a case, which forms binding precedent for future similar disputes.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.