Triple

T26453410
Position Surface form Disambiguated ID Type / Status
Subject Ternate people E665416 entity
Predicate traditionalReligionTerm P19689 FINISHED
Object adat kepercayaan 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: adat kepercayaan | Statement: [Ternate people, traditionalReligionTerm, adat kepercayaan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionalReligionTerm
Context triple: [Ternate people, traditionalReligionTerm, adat kepercayaan]
  • A. traditionalReligionName chosen
    Indicates that an entity has a name specifically associated with a traditional or indigenous religion.
  • B. traditionalReligionHighGod
    Indicates that within a traditional religion, the entity functions as a supreme or highest deity (high god) in that belief system.
  • C. officialReligion
    Indicates that a particular religion is formally recognized and designated as the official or state religion of an entity (such as a country or region).
  • D. traditionalReligionPlace
    Indicates that a place is traditionally associated with the practice, worship, or activities of a particular religion.
  • E. religiousName
    Indicates that an entity has or is known by a name specifically associated with a religious role, identity, or context.
  • 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_69ee883d5040819097dd154643005230 completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f73223675481908c1bc3208c0f5284 completed May 3, 2026, 11:31 a.m.
PD Predicate disambiguation batch_69f7317690108190b3aae2cd2e1d069e completed May 3, 2026, 11:28 a.m.
Created at: April 27, 2026, 12:07 a.m.