Triple
T7301534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Stanley, 3rd Earl of Derby |
E167866
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 16th-century English politician |
C17127
|
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: 16th-century English politician Context triple: [Edward Stanley, 3rd Earl of Derby, instanceOf, 16th-century English politician]
-
A.
15th-century English politician
A 15th-century English politician is a historical figure who participated in the governance and political affairs of England during the 1400s, often through roles in Parliament, royal councils, or local administration.
-
B.
16th-century politician
chosen
A 16th-century politician is a historical public figure who engaged in governance, policy-making, and power negotiations within the complex religious, dynastic, and imperial conflicts of the 1500s.
-
C.
13th-century English politician
A 13th-century English politician was a medieval figure involved in the governance of England, often serving in roles such as a member of Parliament, royal administrator, or local official under the monarchy.
-
D.
16th-century English person
A 16th-century English person is an individual who lived in England between 1501 and 1600, experiencing the social, political, religious, and cultural transformations of the Tudor era.
-
E.
politician of the Stuart period
A politician of the Stuart period is a public officeholder or influential political figure active in the British Isles between 1603 and 1714, operating within the monarchical, parliamentary, and factional structures of Stuart rule.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 3:01 p.m.