Triple

T5641648
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Limerick E124279 entity
Predicate wasViolatedBy P29586 FINISHED
Object later English and Irish Parliaments 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: later English and Irish Parliaments | Statement: [Treaty of Limerick, wasViolatedBy, later English and Irish Parliaments]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasViolatedBy
Context triple: [Treaty of Limerick, wasViolatedBy, later English and Irish Parliaments]
  • A. violationOf chosen
    Indicates that one entity breaches, disobeys, or infringes upon a rule, law, agreement, or right associated with another entity.
  • B. violatedPrinciple
    Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
  • C. violationContext
    Indicates the specific circumstances, conditions, or situational factors under which a violation occurs or is considered to have occurred.
  • D. isBrokenBy
    Indicates that one entity causes another entity to become damaged, nonfunctional, or destroyed.
  • E. allegedViolationSystem
    Indicates a system is reported or suspected to have violated a rule, policy, or regulation, without the violation being legally or formally established.
  • 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_69c00824643c81909ffdb888a2d35189 completed March 22, 2026, 3:17 p.m.
NER Named-entity recognition batch_69c02286a14481908703ec1741343b76 completed March 22, 2026, 5:10 p.m.
PD Predicate disambiguation batch_69c01b2168508190b64b355cf50034ad completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:41 p.m.