Triple
T26215525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felice Orsini |
E655613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 16th-century Italian noble |
C10890
|
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: 16th-century Italian noble Context triple: [Felice Orsini, instanceOf, 16th-century Italian noble]
-
A.
Italian nobleman
chosen
An Italian nobleman is a male member of Italy’s hereditary aristocracy, typically holding a title, land, and social privileges rooted in the country’s historical feudal and courtly traditions.
-
B.
17th-century Italian aristocracy
The 17th-century Italian aristocracy comprised powerful noble families who controlled fragmented city-states and territories through landownership, patronage, and courtly culture, blending feudal traditions with Baroque-era political and artistic influence.
-
C.
Neapolitan aristocrat
A Neapolitan aristocrat is a member of the hereditary upper class of Naples, historically distinguished by noble titles, landownership, and influence over the region’s political and cultural life.
-
D.
Pisan nobleman
A Pisan nobleman is an aristocratic male from the medieval or Renaissance city-state of Pisa, holding hereditary social status, political influence, and often land or mercantile wealth within its civic hierarchy.
-
E.
medieval Italian noblewoman
A medieval Italian noblewoman is an aristocratic woman of the Italian Middle Ages who wields social, economic, and sometimes political influence through lineage, marriage alliances, and the management of estates within a feudal and patriarchal society.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:54 p.m.