Triple
T14924427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainsborough family |
E371595
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early modern English lineage |
C34609
|
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: early modern English lineage Context triple: [Rainsborough family, instanceOf, early modern English lineage]
-
A.
medieval English noble dynasty
A medieval English noble dynasty is a powerful hereditary family line that held titles, lands, and political influence across generations in England during the Middle Ages.
-
B.
English Royalist
An English Royalist is a supporter of the English monarchy who upholds the authority, legitimacy, and traditional privileges of the crown, especially during periods of political conflict or civil war.
-
C.
English Puritan
An English Puritan is a member of a 16th–17th century religious reform movement within the Church of England that sought to "purify" worship and doctrine from perceived Catholic influences, emphasizing strict moral discipline, personal piety, and the authority of Scripture.
-
D.
medieval English name
A medieval English name is a personal name used in England roughly between the 5th and 15th centuries, often reflecting Old English, Norman, or Latin influences and frequently tied to religious, occupational, or locational origins.
-
E.
Middle English manuscript
A Middle English manuscript is a handwritten document produced between the late 11th and late 15th centuries in the Middle English language, often preserving literary, religious, legal, or administrative texts in their original medieval form.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:34 a.m.