Triple
T13632476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Debates in the Several State Conventions on the Adoption of the Federal Constitution |
E325756
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | primary-source compilation |
C6136
|
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: primary-source compilation Context triple: [The Debates in the Several State Conventions on the Adoption of the Federal Constitution, instanceOf, primary-source compilation]
-
A.
historical source
chosen
A historical source is any original material—such as documents, artifacts, recordings, or testimonies—created in the past that provides evidence or information about historical events, people, or conditions.
-
B.
annalistic compilation
An annalistic compilation is a chronological record that systematically arranges events year by year, often combining multiple sources to create a continuous historical narrative.
-
C.
statutory compilation
A statutory compilation is an organized collection of statutes, often arranged by subject or jurisdiction, that consolidates and presents the text of enacted laws in a systematic, accessible format.
-
D.
manuscript collection
A manuscript collection is an organized group of handwritten, typed, or otherwise unpublished documents, often related by creator, subject, or provenance, preserved and managed as a single archival unit.
-
E.
compilation special
A compilation special is a curated program that assembles and edits together selected segments, highlights, or episodes—often with minimal new material—to present them as a single, cohesive viewing experience.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:51 p.m.