Triple
T13614294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malbim |
E325271
|
entity |
| Predicate | placeOfBirth |
P1
|
FINISHED |
| Object | Volochysk |
E881762
|
NE 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: Volochysk | Statement: [Malbim, placeOfBirth, Volochysk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Volochysk Context triple: [Malbim, placeOfBirth, Volochysk]
-
A.
Volochysk
chosen
Volochysk is a town in western Ukraine known as a local administrative and transportation center near the border with Ternopil Oblast.
-
B.
Vishnevo
Vishnevo is a village historically located in the former Second Polish Republic, known today as Wiszniew and situated in present-day Belarus.
-
C.
Moghiliov-Podolsk
Moghiliov-Podolsk is the Romanian name for Mogilev-Podilskyi, a city in western Ukraine located on the Dniester River near the border with Moldova.
-
D.
Borisoglebsk
Borisoglebsk is a small Russian city known for its historical architecture and location on the Vorona River in southwestern Russia.
-
E.
Bolkhov
Bolkhov is a historic town in western Russia known for its old churches and traditional architecture within Oryol Oblast.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0abe1208190a1e0a32dc141d836 |
completed | April 12, 2026, 2:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7a83aeeb48190b92b00366791ab15 |
completed | May 3, 2026, 7:55 p.m. |
Created at: April 9, 2026, 9:50 p.m.