Triple
T16200741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manifesto of the Hindustan Socialist Republican Association |
E393191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revolutionary document |
C27413
|
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: revolutionary document Context triple: [Manifesto of the Hindustan Socialist Republican Association, instanceOf, revolutionary 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.
historical political document
chosen
A historical political document is an official or influential written record produced in a past political context that reflects, shapes, or codifies governmental decisions, ideologies, or power relations of its time.
-
C.
constitutional convention document
A constitutional convention document is the formal written record produced by a constitutional convention that outlines proposed or adopted foundational principles, governmental structures, and legal frameworks for a political entity.
-
D.
revolutionary state
A revolutionary state is a political entity formed and governed by a movement that has overthrown an existing regime, seeking to radically transform social, economic, and political structures according to its ideological goals.
-
E.
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.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:03 a.m.