Triple
T13949713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naberezhnye Chelny |
E335486
|
entity |
| Predicate | renamedToBrezhnev |
P112374
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Naberezhnye Chelny, renamedToBrezhnev, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamedToBrezhnev Context triple: [Naberezhnye Chelny, renamedToBrezhnev, 1982]
-
A.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
B.
wasRenamedBackTo
Indicates that an entity, after having its name changed, was later restored to its previous or original name.
-
C.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
-
D.
renamedAsConstantinopleBy
Indicates that one entity changed the name of another entity to "Constantinople."
-
E.
renamedToMariupolIn
Indicates that an entity was renamed to "Mariupol" in a specified year or time period.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e131c608190b4ffdbada24a3208 |
completed | April 14, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:17 p.m.