Triple

T38128296
Position Surface form Disambiguated ID Type / Status
Subject John III of Penthièvre E952144 entity
Predicate heldClaimsThrough P73422 FINISHED
Object hereditary rights from Joan of Penthièvre 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 rights from Joan of Penthièvre | Statement: [John III of Penthièvre, heldClaimsThrough, hereditary rights from Joan of Penthièvre]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heldClaimsThrough
Context triple: [John III of Penthièvre, heldClaimsThrough, hereditary rights from Joan of Penthièvre]
  • A. hasClaimOn chosen
    Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
  • B. holdsTo
    Indicates that one entity maintains, adheres, or remains committed to another entity, such as a belief, standard, agreement, or condition.
  • C. holdsIn
    Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
  • D. heldAs
    Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
  • E. recognizedClaimsOver
    Indicates that one party has formally acknowledged or accepted the validity of certain claims made by another party.
  • 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_69f76f083548819082bd2bbf53c79e8e completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fcb089a8f881909aa9e722babd43f7 completed May 7, 2026, 3:32 p.m.
PD Predicate disambiguation batch_69fc45666c5c8190913bd632ac0e5b84 completed May 7, 2026, 7:55 a.m.
Created at: May 3, 2026, 4:21 p.m.