Triple
T37241853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Urgell |
E923731
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Catalan title |
C32860
|
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 Catalan title Context triple: [Count of Urgell, instanceOf, medieval Catalan title]
-
A.
medieval court title
A medieval court title is a formal designation granted to an individual within a royal or noble household, defining their rank, duties, and privileges in the governance, ceremony, or administration of the realm.
-
B.
medieval Bulgarian title
A medieval Bulgarian title is a formal rank or designation used within the political, military, or social hierarchy of the First and Second Bulgarian Empires, reflecting authority, function, and status in the feudal system.
-
C.
noble of the Crown of Aragon
chosen
A noble of the Crown of Aragon was a member of the hereditary aristocracy holding titles, lands, and political privileges under the composite medieval monarchy that united Aragon, Catalonia, Valencia, and related territories.
-
D.
Hungarian noble title
A Hungarian noble title is a hereditary or granted rank within the historical social hierarchy of the Kingdom of Hungary, denoting status, privileges, and obligations among the nobility.
-
E.
medieval Rus’ title
A medieval Rus’ title is a formal designation of rank, office, or nobility used in the political and social hierarchy of the East Slavic principalities from roughly the 9th to the 15th centuries.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.