Triple

T21278889
Position Surface form Disambiguated ID Type / Status
Subject Montgomery of Skelmorlie E524462 entity
Predicate typeOfNobleBranch P98292 FINISHED
Object cadet line of Montgomerys 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: cadet line of Montgomerys | Statement: [Montgomery of Skelmorlie, typeOfNobleBranch, cadet line of Montgomerys]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfNobleBranch
Context triple: [Montgomery of Skelmorlie, typeOfNobleBranch, cadet line of Montgomerys]
  • A. nobleHouseType
    Indicates the specific category or classification of a noble house (e.g., royal, ducal, baronial) within a hierarchy or system of nobility.
  • B. producedNobleBranch chosen
    Indicates that one entity gave rise to or resulted in the formation of a particular noble family line or branch.
  • C. nobleRankType
    Indicates the specific category or level of nobility associated with an entity within a hierarchical noble rank system.
  • D. hasNoble
    Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
  • E. associatedNobleFamily
    Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
  • 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_69e0b516293c819089458ea2ec85f85e completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73658f598819098a1192abfa40a12 completed April 21, 2026, 8:33 a.m.
PD Predicate disambiguation batch_69e5f6161dac8190b06009cd180e3ff7 completed April 20, 2026, 9:47 a.m.
Created at: April 16, 2026, 4:02 p.m.