Triple
T12822829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connecticut Practice Book |
E306573
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Connecticut state government publication |
C31932
|
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: Connecticut state government publication Context triple: [Connecticut Practice Book, instanceOf, Connecticut state government publication]
-
A.
New York State government document
A New York State government document is an official record, publication, or communication produced or issued by an agency, department, or office of the New York State government in the course of its public duties.
-
B.
county of Connecticut
A county of Connecticut is an administrative geographic subdivision of the state used primarily for statistical and judicial purposes rather than local government.
-
C.
town in Connecticut
A town in Connecticut is a municipal subdivision of the state with its own local government, defined geographic boundaries, and responsibility for providing community services to its residents.
-
D.
New York State government agency component
A New York State government agency component is an organizational unit within a state agency, such as a division, bureau, or office, that performs specific statutory or administrative functions on behalf of the agency.
-
E.
New York State program
A New York State program is an organized, state-administered initiative designed to deliver specific public services, benefits, or regulatory functions to residents, businesses, or communities within New York State.
- F. None of above. chosen
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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:32 p.m.