Triple
T4238930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bnei Moshe |
E94761
|
entity |
| Predicate | aimedAtPopulation |
P17586
|
FINISHED |
| Object | Jewish intelligentsia |
—
|
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: Jewish intelligentsia | Statement: [Bnei Moshe, aimedAtPopulation, Jewish intelligentsia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedAtPopulation Context triple: [Bnei Moshe, aimedAtPopulation, Jewish intelligentsia]
-
A.
targetedPopulation
chosen
Indicates the group of individuals or entities that an action, intervention, or effect is specifically directed toward.
-
B.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
C.
attractsAgeGroup
Indicates that something tends to draw interest or appeal from people belonging to a particular age group.
-
D.
secondaryAudience
Indicates that an entity is a secondary or additional intended audience or target group for another entity (such as a work, message, or product), beyond the primary audience.
-
E.
categoryOfPeopleServed
Indicates the type or group of people that are the primary recipients or beneficiaries of a service or activity.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e76b6e0819084d0ce137b5ba74e |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.