Triple

T26511021
Position Surface form Disambiguated ID Type / Status
Subject Catherine Fox E669682 entity
Predicate hasComplexPersonalRelationshipsWith P47731 FINISHED
Object Jackson Avery 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: Jackson Avery | Statement: [Catherine Fox, hasComplexPersonalRelationshipsWith, Jackson Avery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasComplexPersonalRelationshipsWith
Context triple: [Catherine Fox, hasComplexPersonalRelationshipsWith, Jackson Avery]
  • A. hasComplicatedRelationshipWith chosen
    Indicates that one entity is involved in a complex, often ambiguous or difficult-to-define interpersonal or relational dynamic with another entity.
  • B. haveRelationshipWith
    Indicates that one entity is in some form of defined relationship or association with another entity.
  • C. influencedByPersonalRelationshipWith
    Indicates that one entity’s decisions, opinions, or actions are shaped or affected by a personal relationship it has with another entity.
  • D. inRelationshipWith
    Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
  • E. hasAllegedRelationshipWith
    Indicates a claimed or suspected relationship between two entities that is not confirmed as factual.
  • 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_69eeb319ec70819090834c2591cf5f1e completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69fddd373cdc8190be1b12e70e4deb1f completed May 8, 2026, 12:55 p.m.
PD Predicate disambiguation batch_69fddc6915a88190ad41e379aa3ede13 completed May 8, 2026, 12:51 p.m.
Created at: April 27, 2026, 1:20 a.m.