Triple
T36450294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimean toponymy |
E897989
|
entity |
| Predicate | involvesRenaming |
P30638
|
FINISHED |
| Object | Soviet-era replacement of Crimean Tatar names |
—
|
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: Soviet-era replacement of Crimean Tatar names | Statement: [Crimean toponymy, involvesRenaming, Soviet-era replacement of Crimean Tatar names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesRenaming Context triple: [Crimean toponymy, involvesRenaming, Soviet-era replacement of Crimean Tatar names]
-
A.
wasRenamedIn
Indicates that an entity changed its name to a different one at or during a specific time or event.
-
B.
contextOfRenaming
chosen
Indicates the situational or historical context in which an entity’s name was or is being changed.
-
C.
formedByRenaming
Indicates that one entity is created or derived from another entity specifically through a change of name.
-
D.
relocatedAndRenamed
Indicates that an entity has moved from one location to another and changed its name as part of that move.
-
E.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: May 3, 2026, 4:10 p.m.