Triple
T30499762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–USSR relations |
E776104
|
entity |
| Predicate | keySovietLeader |
P143326
|
FINISHED |
| Object | Nikita Khrushchev |
—
|
NE NERFINISHED |
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: Nikita Khrushchev | Statement: [India–USSR relations, keySovietLeader, Nikita Khrushchev]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keySovietLeader Context triple: [India–USSR relations, keySovietLeader, Nikita Khrushchev]
-
A.
hasSovietLeaderParticipant
Indicates that a Soviet leader is a participant in the referenced event, action, or relationship.
-
B.
sovietLeaderAtTime
chosen
Indicates that a person was the leader of the Soviet Union at a specified point in time.
-
C.
MuscoviteLeader
Indicates a leadership relationship in which the subject serves as a leader or ruler of Muscovites or the Muscovite state.
-
D.
notableLeaderOnCommunistSide
Indicates that the person served as a prominent or influential leader aligned with the communist side in a particular conflict, movement, or political context.
-
E.
wasWorldLeaderIn
Indicates that an entity held a position as the primary political leader of a specified country or political entity during a particular time period.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6877f55bc81908c8fce4bc1064e69 |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:14 p.m.