Triple

T19529262
Position Surface form Disambiguated ID Type / Status
Subject Jin (Korean state) E488615 entity
Predicate religionAndRituals P17769 FINISHED
Object shamanistic practices 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: shamanistic practices | Statement: [Jin (Korean state), religionAndRituals, shamanistic practices]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religionAndRituals
Context triple: [Jin (Korean state), religionAndRituals, shamanistic practices]
  • A. ritualActivities
    Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
  • B. ritualCategory
    Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
  • C. religiousOrRitualAssociation
    Indicates a connection between entities based on shared religious, spiritual, or ritual practices, roles, or significance.
  • D. practicesReligion chosen
    Indicates that an entity actively follows, observes, or participates in the beliefs, rituals, and customs of a particular religion.
  • E. relatedRitual
    Indicates that one entity is associated with, connected to, or involved in the performance or context of a particular ritual.
  • 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_69d8e8da8bec819081f400199491ccc3 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6363dfd6c8190aaa0b374184965bb completed April 20, 2026, 2:20 p.m.
PD Predicate disambiguation batch_69e514c9c00481909b76bda67957e58b completed April 19, 2026, 5:45 p.m.
Created at: April 10, 2026, 1:41 p.m.