Triple
T23853200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shaliach tzibbur |
E592227
|
entity |
| Predicate | genderPracticeVariesIn |
P70787
|
FINISHED |
| Object | different Jewish denominations |
—
|
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: different Jewish denominations | Statement: [shaliach tzibbur, genderPracticeVariesIn, different Jewish denominations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderPracticeVariesIn Context triple: [shaliach tzibbur, genderPracticeVariesIn, different Jewish denominations]
-
A.
genderPracticeVariesBy
chosen
Indicates that the way gender is expressed, understood, or practiced differs depending on the specific context, group, or setting involved.
-
B.
hasGenderPractice
Indicates a relationship where an entity engages in, follows, or applies a particular gender-related practice, norm, or behavior.
-
C.
genderVariation
Indicates that one entity is a variant or alternative form of another entity that differs specifically in grammatical or biological gender.
-
D.
genderVariant
Indicates that an entity’s gender identity or expression differs from traditional or expected norms associated with their assigned sex or gender.
-
E.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c9887e5c819089437769acf684c4 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.