Triple
T5061045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stepan Arkadyevich Oblonsky |
E114021
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Stepan |
E526578
|
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: Stepan | Statement: [Stepan Arkadyevich Oblonsky, givenName, Stepan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stepan Context triple: [Stepan Arkadyevich Oblonsky, givenName, Stepan]
-
A.
Stepan
chosen
Stepan is the given name of Stephen Timoshenko, a pioneering engineer widely regarded as the father of modern engineering mechanics.
-
B.
Semyon
Semyon is a masculine given name of Russian origin, commonly used in Slavic countries.
-
C.
Pyotr
Pyotr is the Russian given name of Peter Kropotkin, the influential 19th-century anarchist philosopher, geographer, and revolutionary.
-
D.
Vsevolod
Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
-
E.
Anatoly
Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74740ae08190930f1fd57187334e |
completed | March 20, 2026, 4:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bfd42f73b88190bb69bffa6a8b9efe |
completed | March 22, 2026, 11:36 a.m. |
Created at: March 20, 2026, 1:38 p.m.