Triple

T15232009
Position Surface form Disambiguated ID Type / Status
Subject Markgräfin E364025 entity
Predicate roleInFeudalSystem P10606 FINISHED
Object consort of a territorial ruler 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: consort of a territorial ruler | Statement: [Markgräfin, roleInFeudalSystem, consort of a territorial ruler]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInFeudalSystem
Context triple: [Markgräfin, roleInFeudalSystem, consort of a territorial ruler]
  • A. feudalStatus chosen
    Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
  • B. feudalFunction
    Indicates the role or duty an entity holds within a feudal hierarchy, such as obligations, services, or functions owed to or performed for another.
  • C. feudalType
    Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
  • D. roleInMonarchyPeriod
    Indicates that an entity held a specific role or position during a defined period of a monarchy.
  • E. associatedWithFeudalSystem
    Indicates a relationship in which something is connected, linked, or relevant to the structures, practices, or institutions of a feudal system.
  • 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_69d85a0ce24c81909c4d3b6475548c95 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0078e27408190bc13c0ca441f5594 completed April 15, 2026, 9:47 p.m.
PD Predicate disambiguation batch_69deca899d5c8190be4a7c71e1683c69 completed April 14, 2026, 11:15 p.m.
Created at: April 10, 2026, 3:12 a.m.