Triple
T32103313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chernyakhovsk |
E819911
|
entity |
| Predicate | wasRenamedIn |
P173567
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [Chernyakhovsk, wasRenamedIn, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRenamedIn Context triple: [Chernyakhovsk, wasRenamedIn, 1946]
-
A.
wasRenamedBackTo
Indicates that an entity, after having its name changed, was later restored to its previous or original name.
-
B.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
C.
relocatedAndRenamed
Indicates that an entity has moved from one location to another and changed its name as part of that move.
-
D.
willBeRenamedAs
Indicates that an entity is planned or expected to receive a new name specified by another entity.
-
E.
formedByRenaming
Indicates that one entity is created or derived from another entity specifically through a change of name.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b6979318819087408741cae8bfe5 |
completed | May 3, 2026, 2:44 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:26 a.m.