Triple
T10138401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Conformity of the Plan to Republican Principles |
E226918
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | founding-era American political document |
C3444
|
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: founding-era American political document Context triple: [The Conformity of the Plan to Republican Principles, instanceOf, founding-era American political document]
-
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.
colonial American political organization
A colonial American political organization is a group formed in the British North American colonies to coordinate political action, represent local interests, and influence governance and policy before and during the American Revolution.
-
C.
foundational legal document
A foundational legal document is an authoritative written instrument that establishes the core principles, structures, and rules governing a legal system, organization, or relationship.
-
D.
American Revolutionary-era text
chosen
An American Revolutionary-era text is a written work produced in or about the late 18th-century struggle for American independence, reflecting the political, social, and ideological debates of the period.
-
E.
United States federal document
A United States federal document is an official record, form, publication, or communication created, issued, or maintained by a federal agency or branch of the U.S. government in the course of its authorized duties.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 9:06 p.m.