Triple
T25261011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Московский журнал |
E633303
|
entity |
| Predicate | редактор |
P107303
|
FINISHED |
| Object | Николай Михайлович Карамзин |
—
|
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: Николай Михайлович Карамзин | Statement: [Московский журнал, редактор, Николай Михайлович Карамзин]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: редактор Context triple: [Московский журнал, редактор, Николай Михайлович Карамзин]
-
A.
editorInChiefEnd
Indicates the point in time or event when an individual's role as editor-in-chief of a publication or organization comes to an end.
-
B.
editorOfWork
chosen
Indicates that one entity serves as the editor responsible for preparing, revising, or overseeing the content of a particular work.
-
C.
editedBy
Indicates that one entity has revised, modified, or otherwise made editorial changes to another entity.
-
D.
namedEditorInChief
Indicates that one entity has been designated to serve in the role of editor-in-chief for another entity, such as a publication or organization.
-
E.
laterEditor
Indicates that one entity served as an editor of a work at a later time or in a subsequent edition relative to another editor.
- F. None of above.
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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f483935ecc8190979f4ad83b192919 |
completed | May 1, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:13 p.m.