Triple

T27762633
Position Surface form Disambiguated ID Type / Status
Subject Stella Kipps E701507 entity
Predicate closeFamilyMemberOf P171671 FINISHED
Object Arthur Kipps 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: Arthur Kipps | Statement: [Stella Kipps, closeFamilyMemberOf, Arthur Kipps]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: closeFamilyMemberOf
Context triple: [Stella Kipps, closeFamilyMemberOf, Arthur Kipps]
  • A. immediateFamilyMemberOf chosen
    Indicates a close familial relationship where one person is a direct or closely related family member (such as parent, child, sibling, or spouse) of another.
  • B. coveredFamilyMember
    Indicates that one person is included as an eligible dependent or beneficiary under another person’s insurance or benefit coverage.
  • C. familyConnectionTo
    Indicates a familial relationship or bond that exists between two entities, such as by blood, marriage, or adoption.
  • D. closestLivingRelatives
    Indicates that the related entities are the most closely related to each other among all currently living entities, in terms of evolutionary or genealogical proximity.
  • E. familyAssociationWith
    Indicates a familial relationship or connection exists between the referenced 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_69ef6a5193808190816eb7d0020b2d87 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f6a8df16a88190a23820e64a3b1f92 completed May 3, 2026, 1:46 a.m.
PD Predicate disambiguation batch_69f6a751d5e48190a77dcecbe7ef9f0b completed May 3, 2026, 1:39 a.m.
Created at: April 27, 2026, 4:28 p.m.