Triple

T25005502
Position Surface form Disambiguated ID Type / Status
Subject Czernobog E625829 entity
Predicate worshipRegionHistorical P23627 FINISHED
Object Polabian Slavs 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: Polabian Slavs | Statement: [Czernobog, worshipRegionHistorical, Polabian Slavs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: worshipRegionHistorical
Context triple: [Czernobog, worshipRegionHistorical, Polabian Slavs]
  • A. majorRegionOfWorship chosen
    Indicates the primary geographic region where a deity, religion, or cult is predominantly worshipped.
  • B. historicalRegion
    Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
  • C. regionOfReligiousSignificance
    Indicates that a location or area holds recognized religious importance, such as being sacred, holy, or central to religious practices or beliefs.
  • D. historicalFocusRegion
    Indicates that an entity’s primary historical attention, study, or activity is centered on a particular geographic region.
  • E. historicalFaith
    Indicates a relationship where an entity holds or is associated with a religious belief or tradition rooted in historical events, doctrines, or practices.
  • 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_69e2ff26c50481908bc82e799c9e6587 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f453035f508190be83a3d521723acf completed May 1, 2026, 7:15 a.m.
PD Predicate disambiguation batch_69f44d77f6e88190a4643ab2cbef567b completed May 1, 2026, 6:51 a.m.
Created at: April 18, 2026, 6:05 a.m.