Triple

T34345004
Position Surface form Disambiguated ID Type / Status
Subject Eupen-Malmedy E881406 entity
Predicate transferTreaty P89484 FINISHED
Object Treaty of Versailles NE NERFINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Treaty of Versailles | Statement: [Eupen-Malmedy, transferTreaty, Treaty of Versailles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transferTreaty
Context triple: [Eupen-Malmedy, transferTreaty, Treaty of Versailles]
  • A. treaty
    Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
  • B. transferAgreement chosen
    Indicates a formal arrangement in which ownership, rights, or responsibilities are transferred from one party to another.
  • C. treatyAfter
    Indicates that a treaty or formal agreement was established after a specified prior event, condition, or relationship between the entities.
  • D. treatyLeadingToSuccession
    Indicates that a treaty or formal agreement results in or establishes the succession of authority, rights, or control from one party to another.
  • E. treatyConcluded
    Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
  • F. None of above.

Provenance (3 batches)

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_69f349bc55e881908c8e338ef76b0043 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff21cbd9108190a52c0ba42004c669 completed May 9, 2026, noon
PD Predicate disambiguation batch_69ff1faea91881908c626c70bca5100a completed May 9, 2026, 11:51 a.m.
Created at: May 1, 2026, 1:58 a.m.