Triple
T23851249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kremlin doctors' case |
E592173
|
entity |
| Predicate | underLeader |
P105870
|
FINISHED |
| Object | Joseph Stalin |
—
|
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: Joseph Stalin | Statement: [Kremlin doctors' case, underLeader, Joseph Stalin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underLeader Context triple: [Kremlin doctors' case, underLeader, Joseph Stalin]
-
A.
establishedUnderLeader
chosen
Indicates that an entity was founded, created, or formally established during the tenure or authority of a specific leader.
-
B.
supportedLeader
Indicates that one entity actively backed, endorsed, or provided assistance to a particular leader.
-
C.
laterLeader
Indicates that one entity serves as a leader or holds a leadership role at a later time than another specified leader.
-
D.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
-
E.
underboss
Indicates that one entity holds a subordinate but high-ranking leadership role directly beneath another, often acting as their primary deputy or second-in-command.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c987c3208190bf3f210d12106927 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.