Triple
T20033694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania proprietors |
E497203
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proprietary government |
C42776
|
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: proprietary government Context triple: [Pennsylvania proprietors, instanceOf, proprietary government]
-
A.
proprietary governor
A proprietary governor is a colonial-era official or authority figure granted governing powers over a territory by a private owner or chartered company rather than directly by a sovereign state.
-
B.
national government
A national government is the central authority of a sovereign state responsible for creating and enforcing laws, managing public policy, and representing the nation domestically and internationally.
-
C.
proprietary license
A proprietary license is a legal agreement that grants users limited rights to use, but not freely modify or redistribute, software or other intellectual property owned and controlled by a specific individual or organization.
-
D.
secret government agency
A secret government agency is a covert, officially sanctioned organization that operates outside public scrutiny to conduct sensitive intelligence, security, or special operations in the interest of national or global objectives.
-
E.
special-purpose governmental unit
A special-purpose governmental unit is a limited-scope public entity, such as a school district or water authority, created by law to perform a specific governmental function or set of functions within a defined geographic area.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:36 p.m.