Triple
T15929451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stepan Makarov |
E386284
|
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 Makarov, givenName, Stepan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stepan Context triple: [Stepan Makarov, 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.
Stepanovich
Stepanovich is a Russian patronymic derived from the male given name Stepan, traditionally indicating "son of Stepan."
-
C.
Semyon
Semyon is a masculine given name of Russian origin, commonly used in Slavic countries.
-
D.
Pyotr
Pyotr is the Russian given name of Peter Kropotkin, the influential 19th-century anarchist philosopher, geographer, and revolutionary.
-
E.
Pyotr
Pyotr is a Russian masculine given name, equivalent to Peter, commonly borne by notable historical and cultural figures.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156a39abc8190927818f6e185033a |
completed | April 16, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0025ec39a8819081c0cf996bc59416 |
completed | May 10, 2026, 6:30 a.m. |
Created at: April 10, 2026, 4:52 a.m.