Triple

T32845278
Position Surface form Disambiguated ID Type / Status
Subject Sekhemre E840081 entity
Predicate possibleLineage P66151 FINISHED
Object lineage of Pharaoh Menkaura 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: lineage of Pharaoh Menkaura | Statement: [Sekhemre, possibleLineage, lineage of Pharaoh Menkaura]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: possibleLineage
Context triple: [Sekhemre, possibleLineage, lineage of Pharaoh Menkaura]
  • A. basedOnCharacterLineage
    Indicates that one entity is derived from, inspired by, or determined according to the ancestral or familial lineage of a character.
  • B. possibleFamily
    Indicates that two entities could plausibly be related as members of the same family, though the familial relationship is not confirmed.
  • C. sourceOfLineageFor
    Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
  • D. importantLineage
    Indicates that one entity’s ancestry, heritage, or familial line is considered especially significant or influential in relation to another entity or context.
  • E. possibleDescendant chosen
    Indicates that one entity may be a descendant of another, without asserting that the descendant relationship is certain.
  • 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_69f3493ff0888190b51e974eae2a7834 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f73ae120bc8190bff94d38d7a7a00d completed May 3, 2026, 12:09 p.m.
PD Predicate disambiguation batch_69f73a38d0848190aa5139144b8561c6 completed May 3, 2026, 12:06 p.m.
Created at: May 1, 2026, 1:16 a.m.