Triple
T13876345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clerk of Court for the District of Vermont |
E333592
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal court clerkship position |
C8184
|
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: federal court clerkship position Context triple: [Clerk of Court for the District of Vermont, instanceOf, federal court clerkship position]
-
A.
court clerk office
A court clerk office is the administrative hub of a court system responsible for managing case records, processing legal documents, scheduling hearings, and providing procedural information to judges, attorneys, and the public.
-
B.
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.
-
C.
clerical office
A clerical office is a workplace where administrative tasks such as record-keeping, correspondence, data entry, and document management are performed to support an organization’s operations.
-
D.
judicial administrative office
chosen
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.
-
E.
federal court
A federal court is a judicial body established by a national government with authority to hear and decide cases arising under that nation’s constitution, federal laws, and treaties.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.