Triple

T35128389
Position Surface form Disambiguated ID Type / Status
Subject Court Management Office E1014371 entity
Predicate instanceOf P0 FINISHED
Object court administration office 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 administration office
Context triple: [Court Management Office, instanceOf, court administration office]
  • 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. 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.
  • C. 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.
  • D. court organization
    A court organization is the structured system of judicial bodies, roles, and procedures that administer justice within a legal jurisdiction.
  • E. court officeholders
    Court officeholders are individuals who occupy official positions within a royal or noble court, managing its administrative, ceremonial, and personal affairs.
  • 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_69f76dd8b6948190aaa32b081816bd94 completed May 3, 2026, 3:46 p.m.
Created at: May 3, 2026, 4:02 p.m.