Triple
T21276695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marina Tsvetaeva |
E524405
|
entity |
| Predicate | burialPlace |
P196
|
FINISHED |
| Object | Yelabuga |
—
|
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: Yelabuga | Statement: [Marina Tsvetaeva, burialPlace, Yelabuga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yelabuga Context triple: [Marina Tsvetaeva, burialPlace, Yelabuga]
-
A.
Yelabuga
chosen
Yelabuga is a historic town in the Republic of Tatarstan, Russia, known for its preserved merchant architecture and cultural heritage.
-
B.
Kamyshin
Kamyshin is a significant industrial and river port city on the Volga River in southwestern Russia.
-
C.
Ulyanovskoye
Ulyanovskoye is a settlement located along the Sviyaga River in Russia.
-
D.
Ostrogozhsk
Ostrogozhsk is a historic town in Voronezh Oblast, Russia, known as a regional center with roots dating back to the 17th century.
-
E.
Ulyanovka
Ulyanovka is an urban-type settlement in Leningrad Oblast, Russia, situated within the administrative boundaries of Tosnensky District.
- 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736583c08819087a4726538e703e2 |
completed | April 21, 2026, 8:33 a.m. |
Created at: April 16, 2026, 4:02 p.m.