Triple
T25261030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Московский журнал |
E633303
|
entity |
| Predicate | исторический период |
P83770
|
FINISHED |
| Object | эпоха Павла I |
—
|
LITERAL 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: эпоха Павла I | Statement: [Московский журнал, исторический период, эпоха Павла I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: исторический период Context triple: [Московский журнал, исторический период, эпоха Павла I]
-
A.
historical era
chosen
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
-
B.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
C.
историческийПредок
Indicates that one entity is a historical ancestor of another, existing in an earlier time and belonging to its lineage.
-
D.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
E.
historicalIntroductionPeriod
Indicates the time period during which something was first introduced or came into use in a historical context.
- 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_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:13 p.m.