Triple
T35758993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardal yeshivot |
E1033520
|
entity |
| Predicate | communityExpectation |
P47277
|
FINISHED |
| Object | encourage large religious families |
—
|
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: encourage large religious families | Statement: [Hardal yeshivot, communityExpectation, encourage large religious families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityExpectation Context triple: [Hardal yeshivot, communityExpectation, encourage large religious families]
-
A.
communityOutcome
Indicates the result, impact, or consequence that an action, program, or event has on a community as a whole.
-
B.
communityAspect
chosen
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
C.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
D.
communityUsage
Indicates how something is used, adopted, or engaged with by a particular community or group of people.
-
E.
communityBased
Indicates that something is organized, developed, or delivered within and by a local community, emphasizing local participation, control, and 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.