Triple

T11995898
Position Surface form Disambiguated ID Type / Status
Subject Jason Seaver E285528 entity
Predicate knownForRelationship P61561 FINISHED
Object relationship with son Mike Seaver 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: relationship with son Mike Seaver | Statement: [Jason Seaver, knownForRelationship, relationship with son Mike Seaver]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: knownForRelationship
Context triple: [Jason Seaver, knownForRelationship, relationship with son Mike Seaver]
  • A. namedForKnownFor
    Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
  • B. inRelationshipWith chosen
    Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
  • C. formerlyKnownFor
    Indicates that an entity was previously recognized or notable for a particular role, attribute, or activity, but is no longer primarily associated with it.
  • D. knownIn
    Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
  • E. refersToPersonKnownFor
    Indicates that one entity makes reference to a person who is notable or recognized for some specific role, achievement, or characteristic.
  • 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_69d6ab44a77c8190a652f4b27164e4ef completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903b211688190bfe6dd15c3f96d2f completed April 10, 2026, 2:05 p.m.
PD Predicate disambiguation batch_69d902b245cc8190af96a9c2bd9c6250 completed April 10, 2026, 2:01 p.m.
Created at: April 8, 2026, 9:46 p.m.