Triple
T2720925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Continental Congress resolutions |
E60077
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States founding-era document |
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: United States founding-era document Context triple: [Continental Congress resolutions, instanceOf, United States founding-era document]
-
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.
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.
-
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.
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.
-
E.
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.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:55 p.m.