Triple

T32539160
Position Surface form Disambiguated ID Type / Status
Subject Anastasius–Kavadh peace agreement E831668 entity
Predicate appliesToFrontier P10503 FINISHED
Object Byzantine–Sasanian border 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: Byzantine–Sasanian border | Statement: [Anastasius–Kavadh peace agreement, appliesToFrontier, Byzantine–Sasanian border]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesToFrontier
Context triple: [Anastasius–Kavadh peace agreement, appliesToFrontier, Byzantine–Sasanian border]
  • A. frontierWith
    Indicates that two regions or territories share a common boundary or border, especially one marking the edge of settled or controlled area.
  • B. adjustedFrontier chosen
    Indicates that a boundary or limit between entities has been modified or recalibrated from its previous position or state.
  • C. appliedBefore
    Indicates that one action, process, or condition was applied earlier in time than another.
  • D. frontierImplication
    Indicates that one condition or state at a boundary or limit logically leads to, constrains, or entails another condition or state at that boundary.
  • E. appliesFrom
    Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
  • 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_69f34924b1cc8190ad3aca0c0f012a7e completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69feced53a7c819098ec474fb7d514b0 completed May 9, 2026, 6:06 a.m.
PD Predicate disambiguation batch_69fecd9cd5288190aac8b4e04a7ee78e completed May 9, 2026, 6:01 a.m.
Created at: May 1, 2026, 1:02 a.m.