Triple
T7504070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis of Lorraine |
E177340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Lorraine member |
C22481
|
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: House of Lorraine member Context triple: [Francis of Lorraine, instanceOf, House of Lorraine member]
-
A.
Capetian dynasty member
A Capetian dynasty member is an individual belonging by blood or legitimate descent to the royal house founded by Hugh Capet, which ruled France and various European realms from the late 10th century onward.
-
B.
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.
-
C.
House of Wittelsbach member
A House of Wittelsbach member is an individual belonging by birth or legitimate adoption to the historic German noble and royal dynasty that ruled territories such as Bavaria and the Palatinate and provided various European kings and emperors.
-
D.
member of the House of Bourbon
A member of the House of Bourbon is an individual belonging by birth or legitimate descent to the historic European royal dynasty that ruled or influenced several kingdoms, including France, Spain, and Naples.
-
E.
House of Hohenstaufen member
A House of Hohenstaufen member is an individual belonging to the medieval German noble dynasty that produced several Holy Roman Emperors and kings of Germany, Italy, and Sicily between the 12th and 13th centuries.
- 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_69c69f2696688190915a8458f2398211 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:44 p.m.