Triple
T447246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Declaration and Resolves of the First Continental Congress |
E7048
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | foundational document of the United States |
C531
|
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 the United States Context triple: [Declaration and Resolves of the First Continental Congress, instanceOf, foundational document of the United States]
-
A.
founding document
chosen
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
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.
founding treaty
A founding treaty is a formal, binding international agreement that establishes, constitutes, and defines the core structures, powers, and purposes of an international organization or political union.
-
D.
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.
-
E.
U.S. state
A U.S. state is a constituent political entity within the United States that possesses its own government, defined territory, and certain sovereign powers under the federal system established by the U.S. Constitution.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.