Triple

T25112208
Position Surface form Disambiguated ID Type / Status
Subject Hartwell homestead E629025 entity
Predicate hasAncestralTies P34787 FINISHED
Object Hartwell 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: Hartwell family | Statement: [Hartwell homestead, hasAncestralTies, Hartwell family]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAncestralTies
Context triple: [Hartwell homestead, hasAncestralTies, Hartwell family]
  • A. hasAncestralRoots chosen
    Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
  • B. ancestralLinks
    Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, another entity.
  • C. hasFamilialTieTo
    Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
  • D. hasMatrilinealConnection
    Indicates a relationship where one entity is connected to another through a line of descent traced exclusively through female ancestors.
  • E. hasGenealogicalRelation
    Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
  • 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_69e2ff3169d08190973b6061d5009abd completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f5f6baf2d48190a6a4cd6501be87d2 completed May 2, 2026, 1:06 p.m.
PD Predicate disambiguation batch_69f5afd5baac8190bb8ed576813c8591 completed May 2, 2026, 8:03 a.m.
Created at: April 18, 2026, 6:27 a.m.