Triple
T14210100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kozlov |
E352204
|
entity |
| Predicate | usedInImperialRussianMaps |
P113225
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kozlov, usedInImperialRussianMaps, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInImperialRussianMaps Context triple: [Kozlov, usedInImperialRussianMaps, yes]
-
A.
countryDuringTsardom
Indicates that an entity functioned as a country or political unit during the historical period of tsardom.
-
B.
usesSovietSymbols
Indicates that an entity employs or displays symbols associated with the former Soviet Union.
-
C.
joinedRussianEmpire
Indicates that an entity became part of, or was incorporated into, the Russian Empire.
-
D.
imperialRepresentation
Indicates that one entity serves as the official representative or embodiment of an empire or imperial authority in relation to another entity.
-
E.
tsarRussia
Indicates that the subject is the tsar (monarch) who rules over Russia.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61fa8d24819092a8ec5d34c1c799 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:05 a.m.