Triple
T1076147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Office of the Legislative Counsel |
E23843
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legislative support office |
C1315
|
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 support office Context triple: [House Office of the Legislative Counsel, instanceOf, legislative support office]
-
A.
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.
-
B.
office of the United States Congress
chosen
An office of the United States Congress is an organizational unit within the legislative branch that supports the operations, administration, or policymaking functions of the House of Representatives, the Senate, or their joint activities.
-
C.
office of the United States House of Representatives
The office of the United States House of Representatives is an organizational unit that supports the legislative, administrative, and constituent service functions of an individual Representative or House entity.
-
D.
government liaison office
A government liaison office is an organizational unit that facilitates communication, coordination, and collaboration between a government entity and external stakeholders such as other agencies, businesses, or the public.
-
E.
legislative body
A legislative body is an organized group of elected or appointed representatives empowered to create, amend, and repeal laws and oversee government policy within a political system.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:42 p.m.