Triple

T257914
Position Surface form Disambiguated ID Type / Status
Subject Ireland E5475 entity
Predicate historicalRelationship P10260 FINISHED
Object complex history with the United Kingdom 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: complex history with the United Kingdom | Statement: [Ireland, historicalRelationship, complex history with the United Kingdom]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalRelationship
Context triple: [Ireland, historicalRelationship, complex history with the United Kingdom]
  • A. hasFamilialTieTo
    Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
  • B. notableRelative
    Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
  • C. associatedWithDynasty
    Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
  • D. associatedHeir
    Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
  • E. moreDistantlyRelatedTo
    Indicates that one entity is related to another by a more distant or indirect relationship compared to some closer reference relationship.
  • F. None of above. chosen

Provenance (4 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_69a2580a64ac8190ad76e34bb0715b5e completed Feb. 28, 2026, 2:50 a.m.
NER Named-entity recognition batch_69a25f921c2881908821ca2c03815eae completed Feb. 28, 2026, 3:22 a.m.
PD Predicate disambiguation batch_69a25b6b3ea88190bbd858999e42efae completed Feb. 28, 2026, 3:05 a.m.
PDg Predicate description generation batch_69a25f9163f881909232f8aea502cf80 completed Feb. 28, 2026, 3:22 a.m.
Created at: Feb. 28, 2026, 2:55 a.m.