Triple

T28948058
Position Surface form Disambiguated ID Type / Status
Subject Nvarsak Treaty E730932 entity
Predicate instanceOf P0 FINISHED
Object 5th-century treaty C44938 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: 5th-century treaty
Context triple: [Nvarsak Treaty, instanceOf, 5th-century treaty]
  • A. Byzantine–Sasanian treaty chosen
    A Byzantine–Sasanian treaty is a formal diplomatic agreement concluded between the Eastern Roman (Byzantine) Empire and the Sasanian (Sassanid) Persian Empire, typically defining terms of peace, territorial boundaries, tribute, and mutual obligations.
  • B. ancient Greek treaty
    An ancient Greek treaty is a formal, often inscribed agreement between city-states or powers that establishes terms of peace, alliance, or mutual obligations under the sanction of the gods.
  • C. 5th-century text
    A 5th-century text is a written work created or compiled between 401 and 500 CE, reflecting the linguistic, cultural, religious, and intellectual contexts of that historical period.
  • D. medieval political agreement
    A medieval political agreement is a formal or informal pact between rulers, nobles, or institutions that defines mutual obligations—such as protection, allegiance, tribute, or territorial control—within the feudal and dynastic power structures of the Middle Ages.
  • E. 6th-century conflict
    A 6th-century conflict is a historically documented war, battle, or prolonged military-political struggle that occurred between 500 and 599 CE, involving organized groups or states and significantly impacting the societies of that era.
  • F. None of above.

Provenance (1 batch)

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_69f043eb9bcc819091ac7b07aecb6475 completed April 28, 2026, 5:21 a.m.
Created at: April 28, 2026, 8:41 a.m.