Triple

T23143874
Position Surface form Disambiguated ID Type / Status
Subject dipolar theism E577533 entity
Predicate claimsCompatibilityWith P151087 FINISHED
Object religious experience of a responsive God 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: religious experience of a responsive God | Statement: [dipolar theism, claimsCompatibilityWith, religious experience of a responsive God]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: claimsCompatibilityWith
Context triple: [dipolar theism, claimsCompatibilityWith, religious experience of a responsive God]
  • A. requiresCompatibilityWith
    Indicates that one entity can only function correctly or be used if it is compatible with another specified entity.
  • B. compatibleSign
    Indicates that two entities are considered astrologically harmonious or well-matched based on their zodiac signs.
  • C. checksCompatibilityWith
    Indicates that one entity evaluates whether it is compatible or can function harmoniously with another entity.
  • D. compatibleStand
    Indicates that one entity can be properly supported or held by another entity’s stand or mounting system.
  • E. isGenerallyCompatibleWith
    Indicates that two entities can typically function or coexist together without significant conflict, issues, or need for special adaptation.
  • F. None of above. chosen

Provenance (4 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_69e245f8e6248190ba3d58e068b4dccb completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18ecc3710819088ac5d72dad0459a completed April 29, 2026, 4:53 a.m.
PD Predicate disambiguation batch_69ef89f83b108190aaaa1db6221fc163 completed April 27, 2026, 4:08 p.m.
PDg Predicate description generation batch_69ef9b7494f4819088ae59ea3d0ae8ab completed April 27, 2026, 5:23 p.m.
Created at: April 17, 2026, 4 p.m.