Triple

T15693339
Position Surface form Disambiguated ID Type / Status
Subject Alcestis E380389 entity
Predicate spouseSelectionCondition P43165 FINISHED
Object suitor had to yoke a lion and a boar to a chariot 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: suitor had to yoke a lion and a boar to a chariot | Statement: [Alcestis, spouseSelectionCondition, suitor had to yoke a lion and a boar to a chariot]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: spouseSelectionCondition
Context triple: [Alcestis, spouseSelectionCondition, suitor had to yoke a lion and a boar to a chariot]
  • A. choseAsHusband
    Indicates that one entity selected another entity to be her husband, typically as a marital partner.
  • B. marriageClauseCondition chosen
    Indicates that a specific condition or set of conditions related to a marriage clause must be satisfied for the associated legal or contractual effect to apply.
  • C. marriesFor
    Indicates that one entity enters into marriage with another entity specifically for a particular reason, motive, or benefit.
  • D. acceptsMarriageTo
    Indicates that one entity formally agrees to enter into a marriage with another entity.
  • E. spouseCharacteristic
    Indicates that a particular characteristic, trait, or attribute is associated with a person’s spouse within the relationship.
  • 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_69d86d99e860819094b6957cde470f2c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0b4d6b5788190883746ee82c799f5 completed April 16, 2026, 10:07 a.m.
PD Predicate disambiguation batch_69e0051d639481909a10614e8f83e659 completed April 15, 2026, 9:37 p.m.
Created at: April 10, 2026, 4:44 a.m.