Triple

T28764364
Position Surface form Disambiguated ID Type / Status
Subject Princess of Leuchtenberg E726217 entity
Predicate maritalAllianceRole P167931 FINISHED
Object dynastic marriages 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: dynastic marriages | Statement: [Princess of Leuchtenberg, maritalAllianceRole, dynastic marriages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maritalAllianceRole
Context triple: [Princess of Leuchtenberg, maritalAllianceRole, dynastic marriages]
  • A. marriageAllianceWith
    Indicates a formal marital union established between two parties to create or strengthen a political, social, or strategic alliance.
  • B. realmOfMarriageAlliance
    Indicates a relationship where a marriage alliance is formed or exists within, or under the authority of, a particular realm or political domain.
  • C. rivalForMarriageOf
    Indicates that one entity is a romantic competitor with another entity for the opportunity to marry a specific third entity.
  • D. maritalRelations
    Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
  • E. spouseOfRole
    Indicates that one role is the spouse (husband, wife, or equivalent marital partner) of another role.
  • F. None of above. chosen

Provenance (4 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_69f03198be14819098fa74e48b3749bf completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f66e5f7e30819094530abceabd5f43 completed May 2, 2026, 9:36 p.m.
PD Predicate disambiguation batch_69f66abfdaf08190a55f14c70be6fd4d completed May 2, 2026, 9:21 p.m.
PDg Predicate description generation batch_69f66d75a8788190aa9ca2c977429045 completed May 2, 2026, 9:32 p.m.
Created at: April 28, 2026, 6:13 a.m.