Triple

T13050639
Position Surface form Disambiguated ID Type / Status
Subject Jephthah E327438 entity
Predicate daughterFate P3146 FINISHED
Object sacrificed because of his vow 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: sacrificed because of his vow | Statement: [Jephthah, daughterFate, sacrificed because of his vow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: daughterFate
Context triple: [Jephthah, daughterFate, sacrificed because of his vow]
  • A. fate chosen
    Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
  • B. chosenFate
    Indicates that an entity has actively selected or accepted a particular destiny or outcome, rather than having it imposed by external forces.
  • C. daughterOf
    Indicates that one person is the female child (daughter) of another person.
  • D. possibleDaughter
    Indicates that one entity may be the daughter of another, but this relationship is not certain or confirmed.
  • E. daughters
    Indicates that one entity is the female child of another entity.
  • 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_69d8076e64308190904fb5c93517c901 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d98a9829b48190b23624b6b3df4600 completed April 10, 2026, 11:41 p.m.
PD Predicate disambiguation batch_69d9803aca4c8190b1015cd159cc47a9 completed April 10, 2026, 10:56 p.m.
Created at: April 9, 2026, 8:57 p.m.