Triple
T3689740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Marriage |
E78314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century work |
C12979
|
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 work Context triple: [On Marriage, instanceOf, 19th-century work]
-
A.
19th-century organization
A 19th-century organization is a formal group or institution established between 1801 and 1900, typically structured around specific social, political, economic, religious, or cultural goals reflective of that era’s historical context.
-
B.
19th-century organization
A 19th-century organization is a formal group or institution established between 1801 and 1900, typically structured around specific social, economic, political, religious, or cultural goals reflective of that era’s historical context.
-
C.
19th-century legislation
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.
-
D.
19th-century industrial enterprise
A 19th-century industrial enterprise is a large-scale, mechanized business organization that harnesses steam power, factory production, and wage labor to mass-produce goods within emerging capitalist markets.
-
E.
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.
- F. None of above. chosen
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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:26 p.m.