Triple
T35258710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliossana |
E1018308
|
entity |
| Predicate | religionDominantCommunity |
P2986
|
FINISHED |
| Object | Judaism |
—
|
NE NERFINISHED |
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: Judaism | Statement: [Eliossana, religionDominantCommunity, Judaism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionDominantCommunity Context triple: [Eliossana, religionDominantCommunity, Judaism]
-
A.
laterReligionDominant
Indicates that a religion adopted or followed at a later time becomes the dominant or primary religion in the relevant context or entity.
-
B.
dominantReligion
chosen
Indicates the religion that holds primary or majority status within a given group, region, or entity.
-
C.
religionDominantBranch
Indicates that one religious branch is the primary or most prevalent form of a broader religion within a given context or population.
-
D.
religiousBackgroundOfCommunity
Indicates the religious tradition, affiliation, or belief system that characterizes or predominates within a particular community.
-
E.
majorityReligionInUrbanAreas
Indicates that a specified religion is the predominant or most widely practiced faith within the urban areas of a given region or population.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: May 3, 2026, 4:02 p.m.