Triple

T25452735
Position Surface form Disambiguated ID Type / Status
Subject Vrlika E637830 entity
Predicate hasMinorityReligionTradition P79727 FINISHED
Object Eastern Orthodoxy NE NERFINISHED

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: Eastern Orthodoxy | Statement: [Vrlika, hasMinorityReligionTradition, Eastern Orthodoxy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMinorityReligionTradition
Context triple: [Vrlika, hasMinorityReligionTradition, Eastern Orthodoxy]
  • A. religionMinority
    Indicates that the subject’s religion is a minority faith within the relevant population or context.
  • B. ethnicReligionMix
    Indicates a relationship where a group or context involves a combined or overlapping presence of specific ethnic identities and religious affiliations.
  • C. religionSignificantMinorityRegion chosen
    Indicates that a particular religion constitutes a significant minority presence within a specified geographic region.
  • D. hasSecondaryReligion
    Indicates that an entity practices, adheres to, or is associated with a secondary religion in addition to its primary religion.
  • E. hasPrimaryReligionComplex
    Indicates that an entity is primarily associated with, practices, or is characterized by a particular religion or religious complex.
  • 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_69e75db7c5048190b8da9cd7eeedb610 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f60c3b09488190ade1b69ff7f0df0e completed May 2, 2026, 2:37 p.m.
PD Predicate disambiguation batch_69f60b8461ac81908c5bd3d73eed59f4 completed May 2, 2026, 2:34 p.m.
Created at: April 21, 2026, 2:03 p.m.