Triple
T32021115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bat Ayin |
E817691
|
entity |
| Predicate | hasCommunityOrientation |
P122297
|
FINISHED |
| Object | Torah observant |
—
|
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: Torah observant | Statement: [Bat Ayin, hasCommunityOrientation, Torah observant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityOrientation Context triple: [Bat Ayin, hasCommunityOrientation, Torah observant]
-
A.
isCommunityOriented
chosen
Indicates that an entity prioritizes the well-being, needs, and engagement of a community in its actions or decisions.
-
B.
hasCommunityAspect
Indicates that something involves, reflects, or contributes to a shared community dimension, such as collective participation, interaction, or benefit.
-
C.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
D.
hasCommunityContext
Indicates that something exists or occurs within, or is influenced by, a particular community’s social, cultural, or environmental context.
-
E.
hasOrganizingCommunity
Indicates that an event, project, or initiative is organized or coordinated by a specific community or group.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a034ca1a8d88190bd44f33814436e59 |
completed | May 12, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_6a034b591f2481908e05562841c9a3c2 |
completed | May 12, 2026, 3:46 p.m. |
Created at: May 1, 2026, 12:16 a.m.