Triple

T24768263
Position Surface form Disambiguated ID Type / Status
Subject Denton, Yorkshire E619644 entity
Predicate hasNotableFamilySeat P19696 FINISHED
Object Fairfax family NE NERFINISHED

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: Fairfax family | Statement: [Denton, Yorkshire, hasNotableFamilySeat, Fairfax family]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotableFamilySeat
Context triple: [Denton, Yorkshire, hasNotableFamilySeat, Fairfax family]
  • A. laterFamilySeat
    Indicates that one entity serves as a subsequent or later seat, residence, or base for a particular family or lineage, following an earlier one.
  • B. hasFamilySeatSinceCentury
    Indicates that an entity has held its principal family residence or ancestral seat continuously since a specified century.
  • C. hasFamilySeatNear
    Indicates that an entity’s principal family residence or ancestral seat is located in the vicinity of another specified place or entity.
  • D. notableSeat chosen
    Indicates that an entity holds or is associated with a seat, position, or place that is considered notable or significant in some context.
  • E. hasNotableFamilyMembers
    Indicates that an entity is related to one or more family members who are considered notable or significant in some context.
  • 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_69e2fabd04488190a2d13c97be745a2d completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f606c79ad081908369605f72e65ca6 completed May 2, 2026, 2:14 p.m.
PD Predicate disambiguation batch_69f602ce79ec8190b8336c2b9de18ac7 completed May 2, 2026, 1:57 p.m.
Created at: April 18, 2026, 4:28 a.m.