Triple

T8552650
Position Surface form Disambiguated ID Type / Status
Subject Asse Roma–Berlino E202479 entity
Predicate instanceOf P0 FINISHED
Object historical alliance C24628 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: historical alliance
Context triple: [Asse Roma–Berlino, instanceOf, historical alliance]
  • A. treaty-based alliance
    A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
  • B. political-military alliance
    A political-military alliance is a formal agreement between two or more states to coordinate their defense and foreign policies, often including mutual security guarantees and joint military planning.
  • C. early modern political alliance
    An early modern political alliance is a formal or informal agreement between states, dynasties, or political entities from roughly the 15th to 18th centuries to cooperate for mutual security, territorial, economic, or dynastic advantage within a shifting balance-of-power system.
  • D. Catholic military alliance
    A Catholic military alliance is a coalition of armed forces from predominantly Catholic states or groups, formed to defend shared religious, political, or territorial interests under a common Catholic identity.
  • E. ancient Greek alliance
    An ancient Greek alliance is a formal coalition of independent city-states that coordinate their military, political, and sometimes economic actions for mutual defense or shared objectives.
  • F. None of above. chosen

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_69ca832610e08190b3b6c6cd2c250255 completed March 30, 2026, 2:05 p.m.
Created at: March 30, 2026, 6:19 p.m.