Triple
T28868123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemirov |
E729057
|
entity |
| Predicate | timeInRussianEmpire |
P113223
|
FINISHED |
| Object | 18th–early 20th century |
—
|
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: 18th–early 20th century | Statement: [Nemirov, timeInRussianEmpire, 18th–early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInRussianEmpire Context triple: [Nemirov, timeInRussianEmpire, 18th–early 20th century]
-
A.
countryDuringTsardom
Indicates that an entity functioned as a country or political unit during the historical period of tsardom.
-
B.
countryDuringRussianEmpirePeriod
chosen
Indicates that a given country existed or is considered in the context of the historical period of the Russian Empire.
-
C.
timePeriodOfInitialRussianControl
Indicates the time span during which Russia first held control or authority over a given entity or territory.
-
D.
statusInRussianEmpire
Indicates the legal or social standing an entity held within the political and administrative system of the Russian Empire.
-
E.
capitalDuringRussianEmpirePeriod
Indicates that a place served as the capital of a given political entity during the period of the Russian Empire.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 6:49 a.m.