Triple

T28535722
Position Surface form Disambiguated ID Type / Status
Subject Suppiluliuma I E722155 entity
Predicate retaliatedAgainst P45761 FINISHED
Object Egyptian vassal states in Syria after Zannanza’s death 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: Egyptian vassal states in Syria after Zannanza’s death | Statement: [Suppiluliuma I, retaliatedAgainst, Egyptian vassal states in Syria after Zannanza’s death]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: retaliatedAgainst
Context triple: [Suppiluliuma I, retaliatedAgainst, Egyptian vassal states in Syria after Zannanza’s death]
  • A. counterattackBy chosen
    Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
  • B. offenseAgainst
    Indicates that one party has committed a harmful, illegal, or rule-violating act directed against another party or entity.
  • C. belligerentAgainst
    Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
  • D. counterplay
    Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
  • E. repudiatedAfter
    Indicates that one entity formally rejects, disavows, or withdraws support for another entity after a specified time or subsequent event.
  • 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_69f01a5d7ec88190ada2d5be7c06c35d completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f64fda797081909e259eb25d51e206 completed May 2, 2026, 7:26 p.m.
PD Predicate disambiguation batch_69f64cb0d8008190912e1430cfaf92aa completed May 2, 2026, 7:12 p.m.
Created at: April 28, 2026, 3:31 a.m.