Triple

T32111916
Position Surface form Disambiguated ID Type / Status
Subject Treaties of Australia E820140 entity
Predicate instanceOf P0 FINISHED
Object body of international agreements C13347 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: body of international agreements
Context triple: [Treaties of Australia, instanceOf, body of international agreements]
  • A. international agreement
    An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
  • B. corpus of international treaties chosen
    A corpus of international treaties is a structured collection of formal, legally binding agreements between sovereign states and/or international organizations, organized for analysis, reference, and comparative study.
  • C. international agreement package
    An international agreement package is a bundled set of formally negotiated documents, terms, and supporting materials that collectively define and govern a cross-border accord between participating entities or nations.
  • D. private international law instrument
    A private international law instrument is a legal tool—such as a treaty, regulation, or convention—that coordinates which jurisdiction’s laws and courts apply to cross-border private disputes and how foreign judgments are recognized and enforced.
  • E. body of international legal norms
    A body of international legal norms is the coherent set of binding and non-binding rules, principles, and standards that regulate relations and conduct among states and other international actors.
  • 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_69f3490209c881908ec0241476715f15 completed April 30, 2026, 12:20 p.m.
Created at: May 1, 2026, 12:27 a.m.