Triple

T2827877
Position Surface form Disambiguated ID Type / Status
Subject Vipsania Agrippina E54966 entity
Predicate causeOfDivorce P13503 FINISHED
Object political reasons ordered by Augustus 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: political reasons ordered by Augustus | Statement: [Vipsania Agrippina, causeOfDivorce, political reasons ordered by Augustus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: causeOfDivorce
Context triple: [Vipsania Agrippina, causeOfDivorce, political reasons ordered by Augustus]
  • A. divorceReason chosen
    Indicates the reason or cause for which a marriage ended in divorce between two individuals.
  • B. divorceEffect
    Indicates the legal and relational consequences that result from a divorce between two parties.
  • C. causeOf
    Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
  • D. spouseRelationshipEnd
    Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
  • E. mainFamilyLaw
    Indicates that one entity serves as the primary governing family-law framework, rule, or authority for another entity (such as a case, jurisdiction, or legal matter).
  • 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_69ab49e100c0819082a40cb797383243 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abde95d8148190bcae8b0659a5c116 completed March 7, 2026, 8:15 a.m.
PD Predicate disambiguation batch_69abdd0acab881909e8c25cbef83678c completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 9:59 p.m.