Triple
T1058637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Declaration of Rights |
E22854
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | foundational document of American constitutionalism |
C272
|
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: foundational document of American constitutionalism Context triple: [Virginia Declaration of Rights, instanceOf, foundational document of American constitutionalism]
-
A.
founding document
A founding document is an authoritative text that formally establishes an organization, institution, or state by defining its core principles, structure, and governing rules.
-
B.
foundational legal document
chosen
A foundational legal document is an authoritative written instrument that establishes the core principles, structures, and rules governing a legal system, organization, or relationship.
-
C.
written constitution
A written constitution is a formal, codified document that outlines the fundamental principles, structures, powers, and limits of a government, as well as the rights and duties of its citizens.
-
D.
constitutional instrument
A constitutional instrument is a formal legal document or set of provisions that establishes, organizes, or amends the fundamental principles and structures of a state or governing entity.
-
E.
Anglo-American political tradition
The Anglo-American political tradition is a lineage of political thought and institutions rooted in English common law, parliamentary government, and liberal constitutionalism that has shaped the democratic practices of Britain, the United States, and related societies.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:42 p.m.