Triple
T29054154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | קובנה |
E735342
|
entity |
| Predicate | הייתה מרכז יהודי חשוב עד |
P40411
|
FINISHED |
| Object | השואה |
—
|
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: השואה | Statement: [קובנה, הייתה מרכז יהודי חשוב עד, השואה]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: הייתה מרכז יהודי חשוב עד Context triple: [קובנה, הייתה מרכז יהודי חשוב עד, השואה]
-
A.
hasJewishCommunityUntil
Indicates that a place had an established Jewish community that existed there up to a certain end date or period.
-
B.
hadSignificantJewishPopulationBeforeWorldWarII
chosen
Indicates that the subject place or region had a notably large or influential Jewish community prior to the outbreak of World War II.
-
C.
hasJewishCommunityHistory
Indicates that there is a documented history of a Jewish community being present, active, or influential in relation to the subject.
-
D.
hasSignificantJewishCommunity
Indicates that a place or entity possesses a notably large, influential, or historically important Jewish community.
-
E.
historicallyImportantCenter
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
- 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_69f6609061508190ae12005d993e42bc |
completed | May 2, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:10 a.m.