Triple
T7098227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronze Horseman monument |
E165384
|
entity |
| Predicate | inscriptionTextRussian |
P74901
|
FINISHED |
| Object | ПЕТРУ ПЕРВОМУ ЕКАТЕРИНА ВТОРАЯ ЛѢТА 1782 |
—
|
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: ПЕТРУ ПЕРВОМУ ЕКАТЕРИНА ВТОРАЯ ЛѢТА 1782 | Statement: [Bronze Horseman monument, inscriptionTextRussian, ПЕТРУ ПЕРВОМУ ЕКАТЕРИНА ВТОРАЯ ЛѢТА 1782]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionTextRussian Context triple: [Bronze Horseman monument, inscriptionTextRussian, ПЕТРУ ПЕРВОМУ ЕКАТЕРИНА ВТОРАЯ ЛѢТА 1782]
-
A.
inscriptionTranslation
Indicates that a provided text expresses the translated content of a specific inscription.
-
B.
nameInRussian
Indicates that an entity is known or referred to by a specific name when expressed in the Russian language.
-
C.
currentNameInRussian
Indicates the current official name of an entity as expressed in the Russian language.
-
D.
inscriptionsLanguage
Indicates that the language used in the inscriptions on an object or surface is the specified language.
-
E.
titleInRussian
Indicates that an entity’s title is given or recorded in the Russian language.
- F. None of above. chosen
Provenance (4 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e557c0108190891ca1be84f21601 |
completed | March 27, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:42 p.m.