Triple

T13244045
Position Surface form Disambiguated ID Type / Status
Subject Lexington Town Clerk’s Office E315351 entity
Predicate instanceOf P0 FINISHED
Object town clerk’s office C20571 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: town clerk’s office
Context triple: [Lexington Town Clerk’s Office, instanceOf, town clerk’s 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. district office chosen
    A district office is a local administrative center that manages and coordinates government or organizational services, operations, and support within a specific geographic district.
  • D. clerk
    A clerk is an individual responsible for performing routine administrative, record-keeping, and customer service tasks to support the efficient operation of an organization.
  • E. courthouse
    A courthouse is a public building where legal cases are heard and decided, housing courtrooms, judges' chambers, and related judicial offices.
  • 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_69d806b1072881909e46bd212259c5f0 completed April 9, 2026, 8:06 p.m.
Created at: April 9, 2026, 9:23 p.m.