Triple
T2219283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romantic nationalism |
E48103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century political movement |
C881
|
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: 19th-century political movement Context triple: [Romantic nationalism, instanceOf, 19th-century political movement]
-
A.
19th-century conflict
A 19th-century conflict is a large-scale military or political struggle occurring between 1800 and 1899, typically involving nation-states or empires and shaped by industrialization, nationalism, and shifting imperial ambitions.
-
B.
political movement
chosen
A political movement is a collective effort by a group of people, often organized around shared ideas or grievances, seeking to influence or change government policies, social structures, or political power.
-
C.
18th-century organization
An 18th-century organization is a formally or informally structured group of individuals operating during the 1700s to pursue political, economic, social, religious, or intellectual objectives within the historical context of early modern society.
-
D.
20th-century historical event
A 20th-century historical event is a significant occurrence between 1900 and 1999 that influenced political, social, economic, or cultural developments on a regional or global scale.
-
E.
Indian independence movement organization
An Indian independence movement organization is a group formed to plan, coordinate, and execute political, social, or revolutionary activities aimed at ending British colonial rule and achieving self-governance for India.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:46 p.m.