Triple

T37241899
Position Surface form Disambiguated ID Type / Status
Subject Count of Urgell E923731 entity
Predicate titleHeldHereditarily P127258 FINISHED
Object true LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Count of Urgell, titleHeldHereditarily, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: titleHeldHereditarily
Context triple: [Count of Urgell, titleHeldHereditarily, true]
  • A. hereditaryTitleInheritance
    Indicates that a hereditary title is passed from one individual to another according to established rules of succession.
  • B. hereditaryTitleFor chosen
    Indicates that one entity is a hereditary title that is held by, or associated with, another entity, typically passed down through a family line.
  • C. nobleTitleHeldThrough
    Indicates that an entity holds a noble title specifically by virtue of another person’s status, position, or relationship, rather than in their own independent right.
  • D. aristocraticTitleHeldBy
    Indicates that a specific aristocratic or noble title is held or borne by a particular person.
  • E. aristocraticTitleHeldTo
    Indicates that one entity holds or bears an aristocratic or noble title in relation to another entity (such as a person, family, or jurisdiction).
  • F. None of above.

Provenance (3 batches)

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.
NER Named-entity recognition batch_69ffdf47d9608190830ca23d9cef6409 completed May 10, 2026, 1:28 a.m.
PD Predicate disambiguation batch_69ffdf00e2b4819082dd5cb78f316baf completed May 10, 2026, 1:27 a.m.
Created at: May 3, 2026, 4:15 p.m.