Triple
T16742638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Legislative Research Commission |
E406870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legislative service agency |
C26778
|
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: legislative service agency Context triple: [Kentucky Legislative Research Commission, instanceOf, legislative service agency]
-
A.
legislative agency
chosen
A legislative agency is a governmental body that supports, advises, or implements the functions of a legislature by conducting research, drafting bills, providing analysis, or overseeing specific legislative processes.
-
B.
legislative information system
A legislative information system is a digital platform that collects, manages, tracks, and provides access to legislative documents, processes, and activities to support lawmakers, staff, and the public.
-
C.
legislative office wing
A legislative office wing is a dedicated section of a government building that houses the offices and support spaces for legislators and their staff to conduct administrative, research, and constituent-related work.
-
D.
nonpartisan legislative office
A nonpartisan legislative office is an organizational unit within a legislative body that provides neutral, fact-based research, analysis, and administrative support to all members regardless of political affiliation.
-
E.
legislative auditor
A legislative auditor is an official responsible for independently examining and evaluating government agencies’ financial records, performance, and compliance to ensure accountability to the legislature and the public.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.