Triple
T4737053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Taranto |
E105150
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | title of nobility in Italy |
C14301
|
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: title of nobility in Italy Context triple: [Prince of Taranto, instanceOf, title of nobility in Italy]
-
A.
Italian noble title
chosen
An Italian noble title is a hereditary or granted rank of aristocratic status within the historical social hierarchy of Italian states, such as duke, marquis, count, viscount, or baron.
-
B.
Sicilian noble title
A Sicilian noble title is a hereditary or granted rank of aristocratic status specific to the historical Kingdom and island of Sicily, often tied to landholdings, feudal privileges, and social prestige within Sicilian society.
-
C.
title of nobility in the Holy Roman Empire
A title of nobility in the Holy Roman Empire was a hereditary or granted rank (such as duke, prince, count, or baron) that conferred social status, legal privileges, and often territorial authority within the Empire’s feudal hierarchy.
-
D.
Portuguese noble title
A Portuguese noble title is a hereditary or granted rank of honor within Portugal's historical aristocratic hierarchy, denoting social status, privileges, and often territorial associations.
-
E.
Spanish noble title
A Spanish noble title is a hereditary or granted honorific designation within Spain's aristocratic system, conferring social prestige, historical status, and sometimes ceremonial privileges to its holder.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:19 p.m.