Triple
T21345688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John of Savoy |
E526329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Savoyard nobleman |
C27623
|
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: Savoyard nobleman Context triple: [John of Savoy, instanceOf, Savoyard nobleman]
-
A.
Swiss nobleman
A Swiss nobleman is a male member of the historical or contemporary aristocracy of Switzerland, typically associated with hereditary titles, landownership, and regional political influence within the Swiss cantonal system.
-
B.
Savoyard
chosen
A Savoyard is a native or inhabitant of the historical region of Savoy in the western Alps, often associated with its distinct cultural, linguistic, and political heritage.
-
C.
French nobleman
A French nobleman is an aristocratic male from France who holds hereditary or granted titles, privileges, and social status within the traditional hierarchical nobility system.
-
D.
Occitan noble
An Occitan noble is a member of the medieval aristocracy from the Occitan-speaking regions of southern France, characterized by feudal landholding, chivalric culture, and participation in regional courts and politics.
-
E.
11th-century Swiss noble
An 11th-century Swiss noble is a high-ranking landowning aristocrat from the region of present-day Switzerland, wielding military, judicial, and economic power within a feudal hierarchy under larger dynastic or ecclesiastical authorities.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:54 p.m.