Triple
T27244332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine Turnpike Authority |
E687296
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | quasi-independent state agency |
C2542
|
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: quasi-independent state agency Context triple: [Maine Turnpike Authority, instanceOf, quasi-independent state agency]
-
A.
independent regional agency
An independent regional agency is an autonomous public or quasi-public organization that operates within a specific geographic region to plan, coordinate, and deliver specialized services or regulatory functions separate from direct control by central government bodies.
-
B.
independent agency of the United States federal government
An independent agency of the United States federal government is an organization established by Congress that operates outside the executive departments, with a specific mandate and varying degrees of autonomy from presidential control.
-
C.
independent organization
An independent organization is an entity that operates autonomously from external control or affiliation, making its own decisions, policies, and governance.
-
D.
state government agency
chosen
A state government agency is an official public organization established by a state to implement laws, deliver services, and administer specific policy areas within that state’s jurisdiction.
-
E.
bi-state agency
A bi-state agency is a governmental or quasi-governmental organization jointly created and governed by two neighboring states to manage shared resources, infrastructure, or regulatory responsibilities across their common jurisdiction.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 10:40 a.m.