Triple
T25261010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Московский журнал |
E633303
|
entity |
| Predicate | издатель |
P10198
|
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.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
B.
publisherOfWorkAppearingIn
Indicates that an entity is the publisher responsible for issuing a work in which another specified work appears (e.g., as part of a collection, volume, or compilation).
-
C.
publisherRole
Indicates the specific function, capacity, or responsibility an entity has in relation to publishing a work or resource.
-
D.
publisherPerson
chosen
Indicates that a person serves as the publisher (the individual responsible for issuing or releasing) of a given work or resource.
-
E.
publisherImprint
Indicates the publishing imprint or brand under which a work is issued by a publisher.
- 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.