Triple

T36639571
Position Surface form Disambiguated ID Type / Status
Subject Regulation (EC) No 1049/2001 E904546 entity
Predicate basedOnTreatyProvision P99458 FINISHED
Object Article 255 of the EC Treaty 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: Article 255 of the EC Treaty | Statement: [Regulation (EC) No 1049/2001, basedOnTreatyProvision, Article 255 of the EC Treaty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: basedOnTreatyProvision
Context triple: [Regulation (EC) No 1049/2001, basedOnTreatyProvision, Article 255 of the EC Treaty]
  • A. relevantSectionForTreaty
    Indicates that a specific legal or textual section is pertinent or applicable to a given treaty.
  • B. establishedByTreatyOrAct chosen
    Indicates that the relationship or entity was formally created, defined, or authorized through a specific treaty or legislative act.
  • C. isInTreaty
    Indicates that two or more entities are formally bound together by the terms of a treaty or formal agreement.
  • D. cededByTreaty
    Indicates that control or ownership of one entity was formally transferred to another entity as a result of a treaty or formal agreement.
  • E. designedForTreaty
    Indicates that something was created or configured specifically to support, implement, or operate under the terms of a particular treaty.
  • 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_69f76e6c63e48190b1d0c3a79a6c7406 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69ff519b65f081909902ba83b775ef85 completed May 9, 2026, 3:24 p.m.
PD Predicate disambiguation batch_69ff506fccdc8190bd93269589040aed completed May 9, 2026, 3:19 p.m.
Created at: May 3, 2026, 4:11 p.m.