Triple

T44754
Position Surface form Disambiguated ID Type / Status
Subject Douglas (surname) E878 entity
Predicate hasNotableBearers P458 FINISHED
Object members of the House of Douglas 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: members of the House of Douglas | Statement: [Douglas (surname), hasNotableBearers, members of the House of Douglas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotableBearers
Context triple: [Douglas (surname), hasNotableBearers, members of the House of Douglas]
  • A. hasNotableBearer chosen
    Indicates that an entity (such as a name, title, or identifier) is borne by at least one notable person or entity.
  • B. hasNotableMember
    Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
  • C. notableHolder
    Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
  • D. hasNotableFeature
    Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
  • E. hasNotableSubject
    Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
  • 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_69a247a8f6c08190bac804906d62ed5a completed Feb. 28, 2026, 1:40 a.m.
NER Named-entity recognition batch_69a24ba7016481909d595402712db6e2 completed Feb. 28, 2026, 1:57 a.m.
PD Predicate disambiguation batch_69a24abbd32c81908cec461d9097662e completed Feb. 28, 2026, 1:54 a.m.
Created at: Feb. 28, 2026, 1:46 a.m.