Triple
T6603315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colony of Vancouver Island |
E149054
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century polity |
C12804
|
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: 19th-century polity Context triple: [Colony of Vancouver Island, instanceOf, 19th-century polity]
-
A.
19th-century state
chosen
A 19th-century state is a politically organized territorial entity that operated within the 1800s, shaped by industrialization, nationalism, imperial expansion, and evolving concepts of sovereignty and citizenship.
-
B.
19th-century legislation
19th-century legislation encompasses the body of laws and legal reforms enacted during the 1800s that shaped modern nation-states, industrial societies, and evolving civil rights frameworks.
-
C.
19th-century controversy
A 19th-century controversy is a significant public dispute or prolonged debate during the 1800s, often involving social, political, scientific, or religious issues that shaped contemporary thought and policy.
-
D.
19th-century organization
A 19th-century organization is a formal group or institution established between 1801 and 1900, typically structured around specific social, political, economic, religious, or cultural goals reflective of that era’s historical context.
-
E.
19th-century organization
A 19th-century organization is a formal group or institution established between 1801 and 1900, typically structured around specific social, economic, political, religious, or cultural goals reflective of that era’s historical context.
- 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_69c687eaa7508190bb58ce2aa02039b3 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:56 p.m.