Triple

T31639666
Position Surface form Disambiguated ID Type / Status
Subject Battle of Mount Gindarus E807408 entity
Predicate aimOfParthianSide P172873 FINISHED
Object maintain and expand Parthian influence in Syria 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: maintain and expand Parthian influence in Syria | Statement: [Battle of Mount Gindarus, aimOfParthianSide, maintain and expand Parthian influence in Syria]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aimOfParthianSide
Context triple: [Battle of Mount Gindarus, aimOfParthianSide, maintain and expand Parthian influence in Syria]
  • A. ParthianForceType
    Indicates the type or classification of a military force associated with the Parthians.
  • B. ParthianCommander
    Indicates that an entity serves as a military commander within the Parthian context or forces.
  • C. PersianTactics
    Indicates the use or application of military strategies, maneuvers, or methods characteristic of Persian forces in a conflict or battle context.
  • D. methodOfInvasion
    Indicates the specific way or technique by which an invasion is carried out.
  • E. PersianCommander
    Indicates that an entity serves as a military commander for, or in the context of, the Persian forces or Persian polity.
  • 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_69f348d9ce58819093ea2da83cbeeec1 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6b0d21dd08190a9883ff71c94c71c completed May 3, 2026, 2:20 a.m.
PD Predicate disambiguation batch_69f6aca3dedc81908b519d53d2909868 completed May 3, 2026, 2:02 a.m.
PDg Predicate description generation batch_69f6afeaaef88190aefa97e83f8db906 completed May 3, 2026, 2:16 a.m.
Created at: April 30, 2026, 10:49 p.m.