Triple
T21167134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel Mohilever |
E521594
|
entity |
| Predicate | birthPlace |
P1
|
FINISHED |
| Object | Glebokie |
—
|
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: Glebokie | Statement: [Samuel Mohilever, birthPlace, Glebokie]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Glebokie Context triple: [Samuel Mohilever, birthPlace, Glebokie]
-
A.
Obluchye
Obluchye is a small town in Russia’s Far East, located in the Jewish Autonomous Oblast and known primarily as a local railway and administrative center.
-
B.
Glubokoye
chosen
Glubokoye is a town in northeastern Belarus known as a local administrative and cultural center within the Vitebsk Region.
-
C.
Kuibysheve
Kuibysheve is a rural settlement located within Bakhchisarai Raion on the Crimean Peninsula.
-
D.
Borovitskaya
Borovitskaya is a Moscow Metro station located in the city center, providing key interchange access between several central lines.
-
E.
Rybachye
Rybachye is the former name of Balykchy, a town on the western shore of Lake Issyk-Kul in Kyrgyzstan.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7270fce708190a5715b55b406dd4e |
completed | April 21, 2026, 7:28 a.m. |
Created at: April 16, 2026, 3 p.m.