Triple

T2697460
Position Surface form Disambiguated ID Type / Status
Subject Ennead of Heliopolis E58544 entity
Predicate genealogicalStructure P37109 FINISHED
Object three divine generations 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: three divine generations | Statement: [Ennead of Heliopolis, genealogicalStructure, three divine generations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: genealogicalStructure
Context triple: [Ennead of Heliopolis, genealogicalStructure, three divine generations]
  • A. genealogicalLine
    Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
  • B. genealogicalDescription chosen
    Indicates a textual description that explains the genealogical relationships or lineage connections among entities.
  • C. hasGenealogicalInterest
    Indicates a relationship in which one entity has a research, documentation, or personal interest in the family history or lineage of another entity.
  • D. familyGroup
    Indicates that multiple entities are related to each other as members of the same family unit or household.
  • E. ancestralGroup
    Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
  • 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_69ab4ac269e481909cb317d79e68b75b completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abda322af48190833b8a3c006db236 completed March 7, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69abd81ea5d88190ab5c8f8b8064b931 completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:55 p.m.