Triple
T13949714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naberezhnye Chelny |
E335486
|
entity |
| Predicate | nameBrezhnevAbolished |
P112375
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [Naberezhnye Chelny, nameBrezhnevAbolished, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameBrezhnevAbolished Context triple: [Naberezhnye Chelny, nameBrezhnevAbolished, 1988]
-
A.
abolishedDuringGovernmentOf
Indicates that something (such as a law, institution, or practice) was officially ended or eliminated while a particular government was in power.
-
B.
titleAbolishedBy
Indicates that a particular title or rank was formally eliminated or discontinued by a specified authority, event, or legal act.
-
C.
abolishedDuring
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
-
D.
communistRuleEndDate
Indicates the date on which a period of communist governance or control over an entity formally ended.
-
E.
wasAbolishedBy
Indicates that an institution, practice, law, or entity ceased to exist or operate as a result of an action taken by another entity.
- 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.