Triple
T18395266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bečkerek |
E449850
|
entity |
| Predicate | renamedTo |
P3432
|
FINISHED |
| Object | Petrovgrad |
—
|
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: Petrovgrad | Statement: [Bečkerek, renamedTo, Petrovgrad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petrovgrad Context triple: [Bečkerek, renamedTo, Petrovgrad]
-
A.
Petrovgrad
chosen
Petrovgrad was the former name of the Serbian city now known as Zrenjanin, located in the Vojvodina region.
-
B.
Tselinograd
Tselinograd was the Soviet-era name of Kazakhstan’s capital city, now known as Astana.
-
C.
Černilov
Černilov is a municipality and village in the Hradec Králové Region of the Czech Republic, known for its rural character and proximity to the city of Hradec Králové.
-
D.
Slavgorod
Slavgorod is a town in eastern Belarus known for its location near the Sozh River and its historical and regional significance.
-
E.
Kolomna
Kolomna is a historic Russian city southeast of Moscow, known for its well-preserved kremlin, medieval architecture, and traditional pastila confectionery.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e51845d6708190bc96ec801e21b7a3 |
completed | April 19, 2026, 6 p.m. |
Created at: April 10, 2026, 10:46 a.m.