Triple

T31143129
Position Surface form Disambiguated ID Type / Status
Subject Fitzpatrick of Upper Ossory E793843 entity
Predicate associatedBarony P194211 FINISHED
Object Barony of Upper Ossory E1947103 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: Barony of Upper Ossory | Statement: [Fitzpatrick of Upper Ossory, associatedBarony, Barony of Upper Ossory]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedBarony
Context triple: [Fitzpatrick of Upper Ossory, associatedBarony, Barony of Upper Ossory]
  • A. companionBarony
    Indicates a relationship where one barony is designated as an accompanying or associated barony to another, typically linked or paired in status or function.
  • B. hasBarony chosen
    Indicates that one entity possesses or is assigned authority over a barony associated with another entity.
  • C. hasNotableBarony
    Indicates that an entity possesses or is associated with a barony that is considered notable or significant in some context.
  • D. hasNumberOfCompanionBaronies
    Indicates the specific count of companion baronies associated with a given entity.
  • E. associatedWithFeudalOffice
    Indicates a relationship where an entity is linked to, holds, or is otherwise connected with a specific feudal office or position within a feudal system.
  • 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_6a29471c9d0c81909b4a7ca9574d442d completed June 10, 2026, 11:14 a.m.
PD Predicate disambiguation batch_6a0379e5174c8190a0bdde7e381b7624 completed May 12, 2026, 7:05 p.m.
Created at: April 29, 2026, 9:06 p.m.