Triple
T26410685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust in Ukraine |
E663950
|
entity |
| Predicate | appliesToReligiousGroup |
P27867
|
FINISHED |
| Object | Jehovah's Witnesses |
—
|
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: Jehovah's Witnesses | Statement: [Holocaust in Ukraine, appliesToReligiousGroup, Jehovah's Witnesses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToReligiousGroup Context triple: [Holocaust in Ukraine, appliesToReligiousGroup, Jehovah's Witnesses]
-
A.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
B.
isUsedByReligion
Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
-
C.
ethnicOrReligiousGroup
Indicates that one entity is an ethnic or religious group to which the other entity belongs or with which it is associated.
-
D.
hasAssociatedReligion
chosen
Indicates that an entity is connected with or linked to a particular religion.
-
E.
recognizesReligion
Indicates that one entity formally acknowledges or accepts another entity as a valid or legitimate religion.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 26, 2026, 11:37 p.m.