Triple

T8479732
Position Surface form Disambiguated ID Type / Status
Subject Ancient Near East E200484 entity
Predicate religionsIncluded P6676 FINISHED
Object Mesopotamian polytheism 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: Mesopotamian polytheism | Statement: [Ancient Near East, religionsIncluded, Mesopotamian polytheism]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religionsIncluded
Context triple: [Ancient Near East, religionsIncluded, Mesopotamian polytheism]
  • A. religionsPresent chosen
    Indicates that one or more religions are present, practiced, or represented in relation to a given entity or context.
  • B. recognizesReligion
    Indicates that one entity formally acknowledges or accepts another entity as a valid or legitimate religion.
  • C. ethnicReligion
    Indicates that a religion is closely associated with a particular ethnic group, often tied to that group’s culture, ancestry, or identity.
  • D. majorReligionCanBe
    Indicates that an entity can have a particular major religion as one of its possible primary religious affiliations.
  • E. associatedReligionText
    Indicates that there is a textual work (such as a scripture or religious document) that is specifically associated with, or pertains to, a given religion.
  • 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_69ca831b17988190a1f3f3413d57b820 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe5232d008190ae55b982f5fc9e8b completed March 31, 2026, 3:15 p.m.
PD Predicate disambiguation batch_69cbd104250c8190b4c499dcc9937494 completed March 31, 2026, 1:49 p.m.
Created at: March 30, 2026, 6:12 p.m.