Triple
T15886856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebbetzin |
E385212
|
entity |
| Predicate | usedInCommunityType |
P120937
|
FINISHED |
| Object | Orthodox Jewish communities |
—
|
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: Orthodox Jewish communities | Statement: [Rebbetzin, usedInCommunityType, Orthodox Jewish communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCommunityType Context triple: [Rebbetzin, usedInCommunityType, Orthodox Jewish communities]
-
A.
usedInCommunity
Indicates that something is employed, practiced, or applied within a particular community or communal context.
-
B.
usedByCommunity
Indicates that something is utilized or adopted collectively by a particular community.
-
C.
hasCommunityType
Indicates that an entity is associated with or classified under a particular type or category of community.
-
D.
usedByCommunitySize
Indicates that something is utilized or adopted by a community characterized by a particular size or number of members.
-
E.
appliesToCommunity
Indicates that something (such as a rule, policy, feature, or condition) is relevant or applicable to a particular community as a whole.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:51 a.m.