Triple

T35579043
Position Surface form Disambiguated ID Type / Status
Subject Lord of Jarandilla E1028164 entity
Predicate hasFeudalType P57399 FINISHED
Object hereditary lordship 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 lordship | Statement: [Lord of Jarandilla, hasFeudalType, hereditary lordship]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFeudalType
Context triple: [Lord of Jarandilla, hasFeudalType, hereditary lordship]
  • A. isFeudal
    Indicates that one entity holds a feudal relationship to another, typically involving hierarchical obligations such as land tenure, service, or allegiance.
  • B. isFeudalState
    Indicates that a political entity operates under a feudal system, where power is decentralized and structured through hierarchical obligations between lords and vassals.
  • C. feudalType chosen
    Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
  • D. hasFeudalOverlord
    Indicates that one entity holds feudal lordship or overlord authority over another, implying hierarchical control and obligations within a feudal system.
  • E. feudType
    Indicates the specific kind or category of ongoing conflict or long-standing hostility that exists between entities.
  • 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_69f76e0386688190b931bacdc145938c completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fcab6e888881908ca9e18660928a40 completed May 7, 2026, 3:10 p.m.
PD Predicate disambiguation batch_69fc4562a5b88190bad48f083a6dcdfa completed May 7, 2026, 7:55 a.m.
Created at: May 3, 2026, 4:04 p.m.