Triple
T23576199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyzhnytsia |
E580262
|
entity |
| Predicate | hasNotableReligiousTradition |
P77999
|
FINISHED |
| Object | Hasidic Judaism |
—
|
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: Hasidic Judaism | Statement: [Vyzhnytsia, hasNotableReligiousTradition, Hasidic Judaism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableReligiousTradition Context triple: [Vyzhnytsia, hasNotableReligiousTradition, Hasidic Judaism]
-
A.
hasNotableReligiousCommunity
chosen
Indicates that an entity is known for having a significant or prominent religious community associated with it.
-
B.
isNonReligious
Indicates that an entity does not adhere to, practice, or identify with any religion or religious belief system.
-
C.
excludedReligion
Indicates that a particular religion is explicitly not allowed, accepted, or included within a given context, group, or condition.
-
D.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd6608481909a0d293ba8f65b2b |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:38 p.m.