Triple
T17659337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | סקווירא |
E440207
|
entity |
| Predicate | hasToponym |
P20238
|
FINISHED |
| Object | Skvira |
—
|
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: Skvira | Statement: [סקווירא, hasToponym, Skvira]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Skvira Context triple: [סקווירא, hasToponym, Skvira]
-
A.
Skvira
chosen
Skvira is a town in Ukraine historically associated with the Skver Hasidic dynasty and its Jewish community.
-
B.
Dupnitsa
Dupnitsa is a town in southwestern Bulgaria known as a regional center near the Osogovo Mountains, with historical roots and access to mountain tourism and outdoor activities.
-
C.
Izhora
Izhora is a small Finnic ethnic group indigenous to the Ingria region near the eastern Gulf of Finland, known for its distinct Uralic language and traditional culture.
-
D.
Slavgorod
Slavgorod is a town in eastern Belarus known for its location near the Sozh River and its historical and regional significance.
-
E.
Alchevsk
Alchevsk is an industrial city in eastern Ukraine known for its steel and metallurgical plants.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea469448190b2753571f8493aef |
completed | April 19, 2026, 5:56 a.m. |
Created at: April 10, 2026, 9:39 a.m.