Triple

T12130217
Position Surface form Disambiguated ID Type / Status
Subject Osun priestesses E288914 entity
Predicate deityTypeServed P60203 FINISHED
Object river goddess 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: river goddess | Statement: [Osun priestesses, deityTypeServed, river goddess]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: deityTypeServed
Context triple: [Osun priestesses, deityTypeServed, river goddess]
  • A. servedDeity chosen
    Indicates that one entity acted in service, devotion, or worship toward a particular deity.
  • B. typeOfDeity
    Indicates that one entity is classified as a specific kind or category of deity in relation to another.
  • C. mainDeity
    Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
  • D. deityCategory
    Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
  • E. hasDeity
    Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
  • 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_69d6ab4b5e4c81909950b17151eb0951 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d91841615c819097f20a7447a1b8f4 completed April 10, 2026, 3:33 p.m.
PD Predicate disambiguation batch_69d91508f8008190b3a90ec0bf0953ca completed April 10, 2026, 3:19 p.m.
Created at: April 8, 2026, 9:49 p.m.