Triple
T29054157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | קאוונא |
E735342
|
entity |
| Predicate | הייתה מרכז תרבותי יהודי עד |
P140101
|
FINISHED |
| Object | השואה |
—
|
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: השואה | Statement: [קאוונא, הייתה מרכז תרבותי יהודי עד, השואה]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: הייתה מרכז תרבותי יהודי עד Context triple: [קאוונא, הייתה מרכז תרבותי יהודי עד, השואה]
-
A.
hasJewishCommunityUntil
chosen
Indicates that a place had an established Jewish community that existed there up to a certain end date or period.
-
B.
hasJewishCommunityHistory
Indicates that there is a documented history of a Jewish community being present, active, or influential in relation to the subject.
-
C.
hadSignificantJewishPopulationBeforeWorldWarII
Indicates that the subject place or region had a notably large or influential Jewish community prior to the outbreak of World War II.
-
D.
hasCulturalCenterFunction
Indicates that something serves the role or performs the activities of a cultural center, such as hosting cultural events, programs, or services.
-
E.
hasCulturalCentre
Indicates that one entity possesses, hosts, or contains a cultural centre associated with it.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 10:10 a.m.