Triple

T26527747
Position Surface form Disambiguated ID Type / Status
Subject Earl of Devon (English Courtenay branch) E670737 entity
Predicate hasNobleFamilyOrigin P143401 FINISHED
Object medieval Courtenay family of Devon 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: medieval Courtenay family of Devon | Statement: [Earl of Devon (English Courtenay branch), hasNobleFamilyOrigin, medieval Courtenay family of Devon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNobleFamilyOrigin
Context triple: [Earl of Devon (English Courtenay branch), hasNobleFamilyOrigin, medieval Courtenay family of Devon]
  • A. hasNobleHouseOrigin chosen
    Indicates that an entity originates from, or is ancestrally associated with, a particular noble house.
  • B. hasNoble
    Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
  • C. hasNobleStatus
    Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
  • D. associatedNobleFamily
    Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
  • E. motherNobleFamily
    Indicates that a person’s mother belongs to a specified noble family or house.
  • 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_69eeb31ea1e08190b9ff43cf9bc25bf8 completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69fd82ed2a4c81908bd7797fbd2e3d08 completed May 8, 2026, 6:30 a.m.
PD Predicate disambiguation batch_69fd814cc10481908e4f8123d35a5d0c completed May 8, 2026, 6:23 a.m.
Created at: April 27, 2026, 1:33 a.m.