Triple
T34015757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramat Beit Shemesh Bet |
E872236
|
entity |
| Predicate | religiousNorms |
P110894
|
FINISHED |
| Object | modesty-focused public space |
—
|
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: modesty-focused public space | Statement: [Ramat Beit Shemesh Bet, religiousNorms, modesty-focused public space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousNorms Context triple: [Ramat Beit Shemesh Bet, religiousNorms, modesty-focused public space]
-
A.
hasReligiousNorm
chosen
Indicates that one entity prescribes, embodies, or is governed by a religious rule, standard, or expectation in relation to another entity or context.
-
B.
religiousLawView
Indicates a person's stance, interpretation, or opinion regarding a particular religious law or set of religious legal principles.
-
C.
religiousLawAspect
Indicates that one entity represents a specific aspect, dimension, or component of a religious law associated with another entity.
-
D.
religiousAttitude
Indicates an entity’s stance, disposition, or orientation toward religion or religious beliefs.
-
E.
reveredByReligion
Indicates that a religion holds a particular entity in high esteem, veneration, or sacred regard.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: May 1, 2026, 1:51 a.m.