Triple

T30247474
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Misenum E769097 entity
Predicate instanceOf P0 FINISHED
Object ancient Roman treaty C50286 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: ancient Roman treaty
Context triple: [Treaty of Misenum, instanceOf, ancient Roman treaty]
  • A. 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.
  • B. Byzantine–Sasanian treaty
    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.
  • C. Roman state formula
    A Roman state formula is a standardized legal or ceremonial expression used in official Roman documents and rituals to articulate the authority, structure, and obligations of the Roman state.
  • D. ancient Roman
    An ancient Roman is a person from the civilization of Rome between roughly the 8th century BCE and the 5th century CE, characterized by its distinctive language, culture, politics, and engineering achievements.
  • E. peace treaty inscription chosen
    A peace treaty inscription is a formally recorded text, often carved or written on a durable medium, that documents the terms, parties, and context of an agreement to end or prevent conflict.
  • 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_69f224831dc08190b2e569b987264057 completed April 29, 2026, 3:32 p.m.
Created at: April 29, 2026, 7:39 p.m.