Triple
T7120878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act of the Legislative Council of India founding the University of Calcutta |
E165946
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century law |
C10771
|
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 law Context triple: [Act of the Legislative Council of India founding the University of Calcutta, instanceOf, 19th-century law]
-
A.
19th-century legislation
chosen
19th-century legislation encompasses the body of laws and legal reforms enacted during the 1800s that shaped modern nation-states, industrial societies, and evolving civil rights frameworks.
-
B.
19th-century state
A 19th-century state is a politically organized territorial entity that operated within the 1800s, shaped by industrialization, nationalism, imperial expansion, and evolving concepts of sovereignty and citizenship.
-
C.
19th-century work
A 19th-century work is any creative, intellectual, or artistic production—such as a book, painting, musical composition, or scientific treatise—created or first published between 1801 and 1900.
-
D.
19th-century controversy
A 19th-century controversy is a significant public dispute or prolonged debate during the 1800s, often involving social, political, scientific, or religious issues that shaped contemporary thought and policy.
-
E.
early modern legal codification
Early modern legal codification is the systematic collection, organization, and formal enactment of laws in comprehensive written codes by emerging centralized states between roughly the 16th and 18th centuries.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:43 p.m.