Triple
T18399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Union |
E363
|
entity |
| Predicate | blocLeadership |
P981
|
FINISHED |
| Object | leader of the Eastern Bloc |
—
|
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: leader of the Eastern Bloc | Statement: [Soviet Union, blocLeadership, leader of the Eastern Bloc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blocLeadership Context triple: [Soviet Union, blocLeadership, leader of the Eastern Bloc]
-
A.
hasLeader
chosen
Indicates that one entity serves as the leader or head of another entity.
-
B.
headOfGovernmentBody
Indicates that one entity serves as the chief executive or leading official in charge of governing another entity, typically a political or administrative body.
-
C.
executiveBody
Indicates that an entity serves as the executive governing authority or decision-making body for another entity.
-
D.
chairperson
Indicates that one entity serves as the leader or head of a group, committee, or organization in relation to another entity.
-
E.
enactedBy
Indicates that a law, policy, or formal measure is officially established or brought into effect by a specific authority or governing body.
- 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_69a240778d288190815c0052ebbbcc91 |
completed | Feb. 28, 2026, 1:10 a.m. |
| NER | Named-entity recognition | batch_69a246cbca108190a92478df126d9bf8 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a2464f61648190ac690044be194972 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:14 a.m.