Triple

T31142903
Position Surface form Disambiguated ID Type / Status
Subject Ossory kingship line of Mac Giolla Phádraig E793837 entity
Predicate associatedModernSurname P20950 FINISHED
Object Fitzpatrick E224671 NE 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: Fitzpatrick | Statement: [Ossory kingship line of Mac Giolla Phádraig, associatedModernSurname, Fitzpatrick]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedModernSurname
Context triple: [Ossory kingship line of Mac Giolla Phádraig, associatedModernSurname, Fitzpatrick]
  • A. associatedSurname
    Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
  • B. hasModernNamesake
    Indicates that an entity is the namesake or inspiration for a modern entity that shares or derives its name from it.
  • C. isModernName
    Indicates that a given name is considered modern or contemporary in usage or origin, as opposed to traditional or historical.
  • D. hasModernName chosen
    Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
  • E. familyNameSuffix
    Indicates that one entity is the suffix portion (such as “Jr.” or “III”) of another entity’s family name.
  • F. None of above.

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_69f224d2b3a48190aa9dd26fbf6eab1a completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_6a037c876524819098545e6037d3107d completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2a1e1545108190a3a47039c9cb636f completed June 11, 2026, 2:31 a.m.
PD Predicate disambiguation batch_6a0379e5174c8190a0bdde7e381b7624 completed May 12, 2026, 7:05 p.m.
Created at: April 29, 2026, 9:06 p.m.