Triple
T7979665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantine III of Scotland |
E185536
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Alpin |
C23340
|
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 Alpin Context triple: [Constantine III of Scotland, instanceOf, member of the House of Alpin]
-
A.
member of the House of Savoy
A member of the House of Savoy is an individual belonging by birth or marriage to the historic European royal dynasty that ruled territories including Savoy, Sardinia, and eventually unified Italy.
-
B.
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.
-
C.
member of the House of Lorraine
A member of the House of Lorraine is an individual belonging by birth or legitimate descent to the historic European noble dynasty that ruled the Duchy of Lorraine and later held significant royal and imperial titles.
-
D.
member of the House of Reuss
A member of the House of Reuss is an individual belonging to the historic German princely family that ruled various small states in Thuringia, traditionally naming all male members Heinrich (Henry).
-
E.
member of the Livingston family
A member of the Livingston family is an individual who belongs by birth, marriage, or legal adoption to the historically prominent Livingston lineage, sharing its familial identity, heritage, and social ties.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:14 p.m.