Triple

T7066306
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Brussels E164360 entity
Predicate amendmentEffect P774 FINISHED
Object creation of Western European Union LITERAL FINISHED

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: creation of Western European Union | Statement: [Treaty of Brussels, amendmentEffect, creation of Western European Union]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: amendmentEffect
Context triple: [Treaty of Brussels, amendmentEffect, creation of Western European Union]
  • A. effectOfAmendments chosen
    Indicates the causal impact or consequences that specific amendments have on something, such as a law, document, or situation.
  • B. legalAmendment
    Indicates a formal change or modification made to an existing law, regulation, or legal document.
  • C. typeOfAmendment
    Indicates the specific kind or category of amendment that is being applied to something, such as a document, law, or agreement.
  • D. isAmendmentTo
    Indicates that one item formally modifies, revises, or adds to the content or terms of another item.
  • E. proposedAmendment
    Indicates that one entity has formally suggested a change or addition (an amendment) to another entity, such as a document, law, or agreement.
  • 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_69c688796c148190adb2f1596f595f22 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e4a4e7188190aef123ff1a2aa473 completed March 27, 2026, 8:12 p.m.
PD Predicate disambiguation batch_69c6e1bdc1f08190975fcdbbb1854d1e completed March 27, 2026, 7:59 p.m.
Created at: March 27, 2026, 2:39 p.m.