Triple

T27992401
Position Surface form Disambiguated ID Type / Status
Subject MacMartin E706914 entity
Predicate historicalRoleWithinClan P29914 FINISHED
Object sept of Clan Cameron 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: sept of Clan Cameron | Statement: [MacMartin, historicalRoleWithinClan, sept of Clan Cameron]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalRoleWithinClan
Context triple: [MacMartin, historicalRoleWithinClan, sept of Clan Cameron]
  • A. hasHistoricClan
    Indicates that an entity is associated with, or belongs to, a historically recognized clan or lineage group.
  • B. associatedClanChief
    Indicates a relationship where an entity is linked or connected to a particular clan chief, typically as the chief responsible for or representing that entity.
  • C. hasClanStatus
    Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
  • D. roleInHistoryOf
    Indicates that one entity holds a specific role, contribution, or significance within the historical development or narrative of another entity.
  • E. hasHistoricalRoleAs chosen
    Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or 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_69ef96b980d88190a753b2f9a978595a completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69fdb45537288190b6791078d4a6899f completed May 8, 2026, 10 a.m.
PD Predicate disambiguation batch_69fdb39ad96481908376d7def9fafc13 completed May 8, 2026, 9:57 a.m.
Created at: April 27, 2026, 7:51 p.m.