Triple

T32017636
Position Surface form Disambiguated ID Type / Status
Subject Baron MacRobert E817588 entity
Predicate hasHeraldicType P110465 FINISHED
Object barony 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: barony | Statement: [Baron MacRobert, hasHeraldicType, barony]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHeraldicType
Context triple: [Baron MacRobert, hasHeraldicType, barony]
  • A. hasHeraldryType chosen
    Indicates that an entity is associated with a specific category or style of heraldry (such as a type of coat of arms or emblem).
  • B. hasHeraldicRole
    Indicates that an entity holds or is assigned a specific role or function within a heraldic context (such as in coats of arms, armorial bearings, or heraldic ceremonies).
  • C. hasHeraldicOrdinary
    Indicates that an entity bears or includes a specific heraldic ordinary (a basic geometric figure) as part of its coat of arms or heraldic design.
  • D. hasHeraldicSubject
    Indicates that one entity serves as the heraldic subject or emblematic figure depicted on another entity, such as on a coat of arms or shield.
  • E. hasHeraldicOrientation
    Indicates the directional or positional orientation of a heraldic element within a coat of arms or similar heraldic context.
  • 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_69f348f9e5d081908cc3f57c4942af52 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fd0d0ba5c48190bddb3f0e6637544c completed May 7, 2026, 10:07 p.m.
PD Predicate disambiguation batch_69fd0c4324a8819086c90adf46216e0e completed May 7, 2026, 10:03 p.m.
Created at: May 1, 2026, 12:16 a.m.