Triple
T38128261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John III of Penthièvre |
E952144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Penthièvre |
C66205
|
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: member of the House of Penthièvre Context triple: [John III of Penthièvre, instanceOf, member of the House of Penthièvre]
-
A.
member of the House of Dreux
A member of the House of Dreux is an individual belonging to the medieval French noble dynasty that originated as a cadet branch of the Capetian kings and held the county of Dreux and other significant feudal titles.
-
B.
member of the House of Montfort
A member of the House of Montfort is an individual belonging to the medieval French noble family of Montfort, historically influential in European feudal politics, crusades, and territorial lordships.
-
C.
member of the House of Valois
A member of the House of Valois is an individual belonging to the French royal dynasty that ruled France and several related territories from the 14th to the 16th centuries.
-
D.
House of Orléans member
A House of Orléans member is an individual belonging to the cadet branch of the French royal family descended from Philippe I, Duke of Orléans, traditionally associated with significant political, dynastic, and cultural roles in French and European history.
-
E.
member of the House of Artois
A member of the House of Artois is an individual belonging by birth or legitimate lineage to the medieval French noble dynasty that held the County of Artois and its associated titles, lands, and feudal privileges.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.