Triple
T6312817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judenrat of Kraków |
E141544
|
entity |
| Predicate | religiousGroupRepresented |
P7903
|
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: [Judenrat of Kraków, religiousGroupRepresented, Jewish community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousGroupRepresented Context triple: [Judenrat of Kraków, religiousGroupRepresented, Jewish community]
-
A.
religiousGroupMentioned
Indicates that a religious group is referenced or mentioned in the given context or statement.
-
B.
religiousGroupsPresent
chosen
Indicates that one or more religious groups are present or represented in a given context, location, or situation.
-
C.
religiousAffiliation
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
D.
religiousBranchOf
Indicates that one religion, denomination, or sect is a subdivision or offshoot of a larger parent religious tradition.
-
E.
religiousFoundation
Indicates that an entity was established, created, or founded by a religious organization, authority, or tradition.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0649ea98c819086509e175812c6c0 |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.