Triple
T6791939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of the Governor constituent services |
E155952
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public-facing constituent services office |
C21631
|
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: public-facing constituent services office Context triple: [Office of the Governor constituent services, instanceOf, public-facing constituent services office]
-
A.
parliamentary service
Parliamentary service is the professional support and administrative work carried out to assist a parliament in its legislative, oversight, and representative functions.
-
B.
front organization
A front organization is an ostensibly independent entity that is secretly controlled by another group or institution to conceal its activities, influence, or objectives.
-
C.
private office
A private office is an enclosed workspace designated for an individual or small group, providing privacy, reduced noise, and a controlled environment for focused work and confidential activities.
-
D.
public service advocate
A public service advocate is an individual who actively promotes, defends, and advances the interests of the public by influencing policies, raising awareness, and ensuring government and institutions are accountable and responsive to community needs.
-
E.
legal services organization
A legal services organization is an entity that provides legal advice, representation, and related support—often focusing on underserved or specific client groups—through licensed attorneys and legal professionals.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:15 p.m.