Triple
T30086405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ORCA Joint Board |
E764613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit governance body |
C14167
|
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 transit governance body Context triple: [ORCA Joint Board, instanceOf, public transit governance body]
-
A.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
B.
governance entity
A governance entity is an individual, group, or organization with the authority and responsibility to establish, oversee, and enforce rules, policies, and decisions within a defined domain.
-
C.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
D.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
E.
transit agency board
chosen
A transit agency board is a governing body that sets policy, oversees funding and strategic direction, and provides public accountability for a region’s public transportation 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:04 p.m.