Triple
T2715584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koło |
E59958
|
entity |
| Predicate | hasJewishCommunity |
P40411
|
FINISHED |
| Object | yes (historically) |
—
|
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 (historically) | Statement: [Koło, hasJewishCommunity, yes (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJewishCommunity Context triple: [Koło, hasJewishCommunity, yes (historically)]
-
A.
hasJewishInstitution
Indicates that a place, organization, or entity possesses, hosts, or is associated with a Jewish religious, cultural, or educational institution.
-
B.
hasSynagogueUnion
Indicates that there exists an organizational or formal union connecting one synagogue with another synagogue or group of synagogues.
-
C.
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.
-
D.
hasChristianCommunity
Indicates that a place or entity possesses or hosts an established Christian community.
-
E.
hasSynagogueType
Indicates the specific classification or type of synagogue associated with an entity.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda94d3288190bd60bc886e2106c7 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.