Triple
T10567062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles, Duke of Guise |
E249377
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | peer of France |
C28251
|
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: peer of France Context triple: [Charles, Duke of Guise, instanceOf, peer of France]
-
A.
constable of France
The constable of France was the kingdom’s highest military officer, responsible for commanding the royal armies and overseeing martial affairs directly under the king.
-
B.
peer of Great Britain
A peer of Great Britain is a noble holding a hereditary or life title (such as duke, marquess, earl, viscount, or baron) created under the Peerage of Great Britain between the 1707 union of England and Scotland and the 1801 union with Ireland, traditionally granting social rank and, historically, a seat in the House of Lords.
-
C.
peer of Great Britain
A peer of Great Britain is a noble holding a hereditary or life title (such as duke, marquess, earl, viscount, or baron) created under the Peerage of Great Britain between the 1707 Acts of Union and the 1801 formation of the United Kingdom.
-
D.
Regent of France
A Regent of France is an individual appointed to govern the kingdom temporarily on behalf of a monarch who is unable to rule, typically due to minority, absence, or incapacity.
-
E.
peer of the Kingdom of England
A peer of the Kingdom of England is a noble holding one of the hereditary or life dignities (duke, marquess, earl, viscount, or baron) that conferred membership in the English peerage and historically a seat in the House of Lords.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
Created at: April 6, 2026, 12:36 p.m.