Triple
T10349619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulganin |
E243844
|
entity |
| Predicate | hasFeminineForm |
P1613
|
FINISHED |
| Object | Bulganina |
E243844
|
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: Bulganina | Statement: [Bulganin, hasFeminineForm, Bulganina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bulganina Context triple: [Bulganin, hasFeminineForm, Bulganina]
-
A.
Bulganin
chosen
Bulganin is the surname of Nikolai Bulganin, a prominent Soviet politician who served as Premier of the Soviet Union during the 1950s.
-
B.
Barya
Barya is an alternative name for the Nara people, an ethnic group primarily inhabiting parts of Eritrea.
-
C.
Yura
Yura is a common Slavic diminutive form of the male given name Yuri (or Yuriy), often used as a familiar or affectionate nickname.
-
D.
East Belukha
East Belukha is one of the twin summits of Belukha Mountain in the Altai range, known for its glaciated slopes and challenging alpine climbing routes.
-
E.
Krasnokamensk–Bichigt
Krasnokamensk–Bichigt is an international border crossing point linking Russia and Mongolia, facilitating road and trade traffic between the two countries.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e946cbb881909b88536d0107995d |
completed | April 7, 2026, 11:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7951e65948190a25e559ba94be3c7 |
completed | April 9, 2026, 12:01 p.m. |
Created at: April 6, 2026, 11:57 a.m.