Triple

T34419732
Position Surface form Disambiguated ID Type / Status
Subject Petty, Inverness-shire E883492 entity
Predicate hasMedievalTiesTo P122170 FINISHED
Object Moray family NE NERFINISHED

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: Moray family | Statement: [Petty, Inverness-shire, hasMedievalTiesTo, Moray family]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMedievalTiesTo
Context triple: [Petty, Inverness-shire, hasMedievalTiesTo, Moray family]
  • A. medievalAssociation chosen
    Indicates a relationship or involvement between entities specifically within a medieval context, such as shared roles, activities, or affiliations characteristic of the Middle Ages.
  • B. isMedieval
    Indicates that something belongs to, originates from, or is characteristic of the medieval (Middle Ages) period.
  • C. medievalSeeTransferredTo
    Indicates that authority, ownership, or jurisdiction over a medieval ecclesiastical see was formally transferred from one holder or location to another.
  • D. medievalStatus
    Indicates the social, legal, or hierarchical standing an entity holds within a medieval societal structure.
  • E. hasMedievalElements
    Indicates that something incorporates characteristics, motifs, or features typical of the medieval period.
  • 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_69f349c2e3b88190a67834eb5bcffeaf completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ff14d596e88190be5263b7f96a96cd completed May 9, 2026, 11:04 a.m.
PD Predicate disambiguation batch_69ff13f0208081909369aeb3b77a6b1f completed May 9, 2026, 11:01 a.m.
Created at: May 1, 2026, 2 a.m.