Triple

T26031900
Position Surface form Disambiguated ID Type / Status
Subject Baron Scott of Tindale E647451 entity
Predicate typeOfFeudalHonor P106301 FINISHED
Object hereditary peerage 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: hereditary peerage | Statement: [Baron Scott of Tindale, typeOfFeudalHonor, hereditary peerage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfFeudalHonor
Context triple: [Baron Scott of Tindale, typeOfFeudalHonor, hereditary peerage]
  • A. feudType
    Indicates the specific kind or category of ongoing conflict or long-standing hostility that exists between entities.
  • B. feudalType
    Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
  • C. typeOfFeudalGrant
    Indicates the specific kind or category of feudal grant that characterizes the relationship between a grantor and a grantee within a feudal system.
  • D. feudalStatus
    Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
  • E. isFeudalTitle chosen
    Indicates that the subject is a title associated with a feudal hierarchy, such as those held within a system of lords, vassals, and land-based obligations.
  • 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_69e77e8b60e88190a3b26c4f0032a2c2 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f7bbf906d8819099020e548dd56bc9 completed May 3, 2026, 9:19 p.m.
PD Predicate disambiguation batch_69f7b9a2dcf88190a7c9e109e41267be completed May 3, 2026, 9:09 p.m.
Created at: April 22, 2026, 9:06 a.m.