Triple
T19404774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arsen |
E485423
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Arseny |
—
|
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: Arseny | Statement: [Arsen, hasVariant, Arseny]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arseny Context triple: [Arsen, hasVariant, Arseny]
-
A.
Arseny
chosen
Arseny is a masculine given name of Russian origin, historically borne by several notable figures in literature, art, and public life.
-
B.
Lopukhin
Lopukhin is a Russian surname historically associated with a noble family of the Russian Empire.
-
C.
Grigory
Grigory is a masculine given name of Russian origin, historically borne by notable figures such as statesman and nobleman Grigory Orlov.
-
D.
Grigory Spiridov
Grigory Spiridov was a prominent 18th-century Russian admiral best known for his leadership in the Russo-Turkish War, particularly at the Battle of Chesma.
-
E.
Ignatyev
Ignatyev is a Russian surname borne by various notable figures in politics, military, sports, and the arts.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6257a361c8190bf019fc350faa225 |
completed | April 20, 2026, 1:09 p.m. |
Created at: April 10, 2026, 1:36 p.m.