Triple

T26759836
Position Surface form Disambiguated ID Type / Status
Subject Adèle Varens E674768 entity
Predicate possibleBiologicalFather P46317 FINISHED
Object Edward Fairfax Rochester 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: Edward Fairfax Rochester | Statement: [Adèle Varens, possibleBiologicalFather, Edward Fairfax Rochester]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: possibleBiologicalFather
Context triple: [Adèle Varens, possibleBiologicalFather, Edward Fairfax Rochester]
  • A. hasPossibleFather chosen
    Indicates a relationship where a given individual may be the father of another, but this parentage is not confirmed.
  • B. possibleFatherInLaw
    Indicates that one person is a potential or candidate father-in-law of another, typically as the (possible) father of that person’s spouse or prospective spouse.
  • C. biologicalParent
    Indicates that one entity is the natural (genetic) parent of another entity.
  • D. possibleMother
    Indicates that one entity could be the biological or adoptive mother of another, but this relationship is uncertain or not definitively established.
  • E. surrogateFatherOf
    Indicates that one entity serves as a surrogate father to another, fulfilling a paternal role without being the biological father.
  • 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_69eecda6e9dc81908452fab3ba17ed9b completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f6640168948190811bd5f933a87cf5 completed May 2, 2026, 8:52 p.m.
PD Predicate disambiguation batch_69f6633451948190bcc0410602bb4914 completed May 2, 2026, 8:48 p.m.
Created at: April 27, 2026, 3:57 a.m.