Triple
T21372255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fyodor Golovin |
E527095
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Golovin |
—
|
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: Golovin | Statement: [Fyodor Golovin, familyName, Golovin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Golovin Context triple: [Fyodor Golovin, familyName, Golovin]
-
A.
Golovin
chosen
Golovin is a Russian surname historically borne by various notable figures in politics, the military, and the arts.
-
B.
Yezernitsky
Yezernitsky is a Jewish surname most notably associated with Yitzhak Shamir, the former Prime Minister of Israel, who was born Yitzhak Yezernitsky.
-
C.
Golymin
Golymin is a village in east-central Poland best known as the site of a significant engagement during the Napoleonic Wars.
-
D.
Surovikin
Surovikin is a Russian army general known for his prominent command roles in the Syrian civil war and the 2022 invasion of Ukraine.
-
E.
Gogolin
Gogolin is a small town in southwestern Poland known for its Silesian cultural heritage and location within the Opole region.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0b0d5ec81908da8f38380dbdc7a |
completed | April 22, 2026, 11:27 a.m. |
Created at: April 16, 2026, 5:10 p.m.