Triple
T9938522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Końskie |
E194017
|
entity |
| Predicate | hasJewishCommunityHistory |
P91263
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Końskie, hasJewishCommunityHistory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJewishCommunityHistory Context triple: [Końskie, hasJewishCommunityHistory, yes]
-
A.
hadSignificantJewishPopulationBeforeWorldWarII
Indicates that the subject place or region had a notably large or influential Jewish community prior to the outbreak of World War II.
-
B.
hasJewishInstitution
Indicates that a place, organization, or entity possesses, hosts, or is associated with a Jewish religious, cultural, or educational institution.
-
C.
isSometimesOfJewishOrigin
Indicates that the entity is occasionally, but not always, derived from or associated with Jewish origin.
-
D.
hasHistoricCommunity
Indicates that an entity is associated with, contains, or is part of a community of historical significance.
-
E.
hasChristianCommunity
Indicates that a place or entity possesses or hosts an established Christian community.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5e64760819094f599f158d32f33 |
completed | April 2, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:44 p.m.