Triple
T3149207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clerk of the United States Tax Court |
E65835
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | court clerk 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: court clerk position Context triple: [Clerk of the United States Tax Court, instanceOf, court clerk 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.
court office
A court office is an administrative unit within a judicial system responsible for managing case records, scheduling hearings, processing legal documents, and supporting the day-to-day operations of the court.
-
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 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.
-
E.
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.
- 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:05 p.m.