Triple

T17800855
Position Surface form Disambiguated ID Type / Status
Subject Diodotus I E444419 entity
Predicate changeOfAllegiance P128974 FINISHED
Object independence from Seleucid Empire 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: independence from Seleucid Empire | Statement: [Diodotus I, changeOfAllegiance, independence from Seleucid Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: changeOfAllegiance
Context triple: [Diodotus I, changeOfAllegiance, independence from Seleucid Empire]
  • A. hadAllegiance
    Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
  • B. changesAllianceOf
    Indicates that one entity causes or initiates a change in the alliance or affiliation status of another entity.
  • C. defectedTo
    Indicates that an entity abandoned its original side, group, or allegiance and joined or gave support to another, typically opposing, side.
  • D. allianceShiftedFrom
    Indicates that an entity changed its alliance from one party or group to another.
  • E. allegiance
    Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
  • F. None of above. chosen

Provenance (4 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_69d8b9efe370819095cd219b143ae727 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e487ff42108190b82ceb4466aa2dff completed April 19, 2026, 7:45 a.m.
PD Predicate disambiguation batch_69e3d8de28688190844b65acf6af54e6 completed April 18, 2026, 7:17 p.m.
PDg Predicate description generation batch_69e3db7704588190a34a422421152173 completed April 18, 2026, 7:28 p.m.
Created at: April 10, 2026, 10:13 a.m.