Triple

T14425463
Position Surface form Disambiguated ID Type / Status
Subject Sir Lachlan Hector Charles Maclean of Duart and Morvern E357684 entity
Predicate clanRole P28158 FINISHED
Object hereditary chief 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: hereditary chief | Statement: [Sir Lachlan Hector Charles Maclean of Duart and Morvern, clanRole, hereditary chief]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: clanRole
Context triple: [Sir Lachlan Hector Charles Maclean of Duart and Morvern, clanRole, hereditary chief]
  • A. clanSystem
    Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
  • B. clanType
    Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
  • C. clanOrSocietySystem
    Indicates a relationship where a group is organized or structured according to a particular clan or society system.
  • D. hasClanStatus chosen
    Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
  • E. clanChiefRecognition
    Indicates that an individual is formally acknowledged or endorsed as a chief by a particular clan or its traditional authority.
  • 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_69d8279402a88190821ffa39ae15bccf completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91123f848190ba3fb18a76c2d24c completed April 14, 2026, 7:10 p.m.
PD Predicate disambiguation batch_69de5c30467881908e770e3940295641 completed April 14, 2026, 3:24 p.m.
Created at: April 10, 2026, 1:18 a.m.