Triple

T31993201
Position Surface form Disambiguated ID Type / Status
Subject Battle of Echmiadzin (1804) E816922 entity
Predicate opposingEmpire1 P4567 FINISHED
Object Russian Empire NE NERFINISHED

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: Russian Empire | Statement: [Battle of Echmiadzin (1804), opposingEmpire1, Russian Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: opposingEmpire1
Context triple: [Battle of Echmiadzin (1804), opposingEmpire1, Russian Empire]
  • A. opposingAlliance
    Indicates that two entities belong to rival or mutually opposed alliances or factions.
  • B. associatedEmpire
    Indicates a relationship where one entity is linked or connected to a particular empire, typically as belonging to, originating from, or being under the influence or control of that empire.
  • C. opposingForce chosen
    Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
  • D. archenemyOf
    Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
  • E. opponentMonarch
    Indicates that one monarch stands in an opposing or adversarial position to another monarch, typically in conflict or competition.
  • 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_69f348f8002081909a3588758ba94afb completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fbbc49da8c8190902bbb05d2477cab completed May 6, 2026, 10:10 p.m.
PD Predicate disambiguation batch_69fbb13f34b08190bbbb220ac1e6e666 completed May 6, 2026, 9:23 p.m.
Created at: May 1, 2026, 12:13 a.m.