Triple
T655947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Politburo of the Communist Party of the Soviet Union |
E11648
|
entity |
| Predicate | dateRestoredName |
P17995
|
FINISHED |
| Object | 1966 |
—
|
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: 1966 | Statement: [Politburo of the Communist Party of the Soviet Union, dateRestoredName, 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRestoredName Context triple: [Politburo of the Communist Party of the Soviet Union, dateRestoredName, 1966]
-
A.
nameRestored
Indicates that an entity’s original or correct name has been reinstated after having been changed, lost, or altered.
-
B.
restoredBy
Indicates that an entity has been returned to a previous or improved state through the actions or intervention of another entity.
-
C.
restored
Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
-
D.
formerName
Indicates that an entity was previously known by a different name in the past.
-
E.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4d57688190a9515ac494a97b22 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d121cec81909986c91291bb4ca8 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49ee356c0819085e2e82831cf1360 |
completed | March 1, 2026, 8:17 p.m. |
Created at: March 1, 2026, 7:36 p.m.