Triple
T25176783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heritage Division (occasional / historical matters) |
E630469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | court administrative unit |
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 administrative unit Context triple: [Heritage Division (occasional / historical matters), instanceOf, court administrative unit]
-
A.
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.
-
B.
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.
-
C.
branch court
A branch court is a subsidiary judicial facility or division located away from a main courthouse to provide more accessible legal services within a specific geographic area.
-
D.
judicial district
A judicial district is a defined geographic area within which a particular court or set of courts has legal authority to hear and decide cases.
-
E.
court section
A court section is a distinct organizational unit within a court system responsible for handling specific types of cases, administrative functions, or judicial processes.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 12:34 p.m.