Triple
T15560863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simeon of Moscow |
E370992
|
entity |
| Predicate | knownAs |
P39
|
FINISHED |
| Object | Simeon Gordyi |
E248607
|
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: Simeon Gordyi | Statement: [Simeon of Moscow, knownAs, Simeon Gordyi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Simeon Gordyi Context triple: [Simeon of Moscow, knownAs, Simeon Gordyi]
-
A.
Grigori
Grigori is the given name of Grigori Rasputin, the controversial Russian mystic and advisor to the Romanov royal family in the early 20th century.
-
B.
Gavril
Gavril is a masculine given name, commonly used in Slavic and Eastern European cultures, that derives from the Hebrew name Gabriel.
-
C.
Grigory
Grigory is a masculine given name of Russian origin, historically borne by notable figures such as statesman and nobleman Grigory Orlov.
-
D.
Semyon
chosen
Semyon is a masculine given name of Russian origin, commonly used in Slavic countries.
-
E.
Alecu
Alecu is a Romanian masculine given name, commonly used as a diminutive or familiar form of Alexandru.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ddb4c0c81909b3f4c75c91f7f3f |
completed | April 16, 2026, 2:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4c4046c08190a43bd5577a97f33d |
completed | May 9, 2026, 3:01 p.m. |
Created at: April 10, 2026, 4:09 a.m.