Triple

T34692158
Position Surface form Disambiguated ID Type / Status
Subject Third session of the AVNOJ E890928 entity
Predicate instanceOf P0 FINISHED
Object session of the AVNOJ C28871 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: session of the AVNOJ
Context triple: [Third session of the AVNOJ, instanceOf, session of the AVNOJ]
  • A. session of AVNOJ chosen
    A session of AVNOJ is a formal meeting of the Anti-Fascist Council for the National Liberation of Yugoslavia where political, legislative, and organizational decisions concerning the wartime resistance and postwar state structure were debated and adopted.
  • B. Loya Jirga
    Loya Jirga is a traditional grand assembly in Afghanistan, composed of tribal elders, community leaders, and political figures, convened to make major national decisions on issues such as constitutional changes, peace, and governance.
  • C. Zemsky Sobor
    Zemsky Sobor was a representative assembly in 16th–17th century Russia, convened by the tsar to consult nobles, clergy, and other estates on major state matters such as succession, legislation, and foreign policy.
  • D. Yugoslav military government
    The Yugoslav military government was a temporary administrative authority established and run by Yugoslav armed forces to control, govern, and reorganize territories under their occupation or liberation, typically during and immediately after World War II.
  • E. pan-Slavic congress
    A pan-Slavic congress is a formal gathering of representatives from various Slavic nations or communities aimed at discussing and promoting shared cultural, political, and social interests across the Slavic world.
  • 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_69f349db7ab8819086808e833f472871 completed April 30, 2026, 12:23 p.m.
Created at: May 1, 2026, 2:05 a.m.