Triple
T36450315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russification of place names in Crimea |
E897990
|
entity |
| Predicate | replacesToponymsOf |
P196565
|
FINISHED |
| Object | Crimean Tatars |
E6711
|
NE 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: Crimean Tatars | Statement: [Russification of place names in Crimea, replacesToponymsOf, Crimean Tatars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesToponymsOf Context triple: [Russification of place names in Crimea, replacesToponymsOf, Crimean Tatars]
-
A.
replacedByToponym
Indicates that one name or designation has been superseded and is now represented or referred to by a toponym (a place-based name).
-
B.
includesToponym
Indicates that one entity contains or references a place name (toponym) associated with another entity.
-
C.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
D.
replacesCapitalCity
Indicates that one capital city is substituted for or takes over the role of another as the official capital.
-
E.
hasToponymicDerivatives
Indicates that a name or term serves as the source from which related place-based or toponymic names are derived.
- F. None of above. chosen
Provenance (5 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39c4346744819092dc3a6a1632c8e6 |
completed | June 22, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
| PDg | Predicate description generation | batch_69fe5c196f4081908f150d4cd6c528fa |
completed | May 8, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:10 p.m.