Triple
T11924284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Montpellier |
E283740
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval feudal title |
C27746
|
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: medieval feudal title Context triple: [Lord of Montpellier, instanceOf, medieval feudal title]
-
A.
medieval nobility
Medieval nobility comprised the hereditary warrior-elite who held land from a monarch in exchange for military and political service, dominating social, economic, and legal life in feudal Europe.
-
B.
title of chivalry
A title of chivalry is an honorific rank or designation bestowed, often by a sovereign or recognized authority, to acknowledge an individual's exemplary bravery, service, or adherence to the ideals of knighthood.
-
C.
peerage title
A peerage title is a hereditary or life rank of nobility granted by a sovereign, conferring social status and often certain legal or ceremonial privileges within a hierarchical aristocratic system.
-
D.
medieval political status
chosen
Medieval political status refers to the hierarchical position and associated rights, duties, and privileges of individuals or groups within the feudal and monarchical power structures of the Middle Ages.
-
E.
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.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:45 p.m.