Triple

T4266126
Position Surface form Disambiguated ID Type / Status
Subject Punt E96827 entity
Predicate religiousImportanceFor P6906 FINISHED
Object ancient Egyptian religion 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: ancient Egyptian religion | Statement: [Punt, religiousImportanceFor, ancient Egyptian religion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religiousImportanceFor
Context triple: [Punt, religiousImportanceFor, ancient Egyptian religion]
  • A. religionSignificant chosen
    Indicates that a particular religion plays an important or influential role in relation to the referenced entity or context.
  • B. laterReligiousSignificance
    Indicates that the subject acquires or is recognized as having religious importance or sacred status at a time subsequent to the period or context initially under consideration.
  • C. religiousTarget
    Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
  • D. religiousFunction
    Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
  • E. religiousSignificanceViaDescendant
    Indicates that something holds religious significance specifically because of, or through, one of its descendants.
  • 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_69b34543f06c8190915ebb1a4574ffa9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34fcc383c81908e17da7cbc86a630 completed March 12, 2026, 11:44 p.m.
PD Predicate disambiguation batch_69b347f8dcb08190a725c1f7fb5a7466 completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:07 p.m.