Triple
T29080101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Działoszyce |
E733950
|
entity |
| Predicate | hasFormerReligiousCommunity |
P183719
|
FINISHED |
| Object | Jewish community |
—
|
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 community | Statement: [Działoszyce, hasFormerReligiousCommunity, Jewish community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerReligiousCommunity Context triple: [Działoszyce, hasFormerReligiousCommunity, Jewish community]
-
A.
formerReligiousAffiliation
Indicates that an entity previously adhered to a particular religion or religious denomination but no longer does so.
-
B.
hasFormerReligiousJurisdiction
Indicates that an entity was previously under the religious authority or governance of another entity, but no longer is.
-
C.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
D.
religiousBackgroundOfCommunity
Indicates the religious tradition, affiliation, or belief system that characterizes or predominates within a particular community.
-
E.
hasReligiousMovement
Indicates that an entity is associated with, follows, or is characterized by a particular religious movement.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: April 28, 2026, 10:54 a.m.