Triple
T36259970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czechoslovak parliamentary election of 1948 |
E892052
|
entity |
| Predicate | supervisingPowerInfluence |
P6502
|
FINISHED |
| Object | Soviet Union |
—
|
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: Soviet Union | Statement: [Czechoslovak parliamentary election of 1948, supervisingPowerInfluence, Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supervisingPowerInfluence Context triple: [Czechoslovak parliamentary election of 1948, supervisingPowerInfluence, Soviet Union]
-
A.
supervisingPowerContext
Indicates a contextual relationship in which one entity holds supervisory authority or oversight power over another.
-
B.
exercisedPowerOver
chosen
Indicates that one entity exerted control, influence, or authority over another entity.
-
C.
supervisionOf
Indicates that one entity oversees, directs, or manages the work, behavior, or activities of another entity.
-
D.
isUnderInfluenceOf
Indicates that one entity is affected, controlled, or significantly shaped by the power, authority, or effect of another entity.
-
E.
subjectOfPower
Indicates that one entity holds authority, control, or influence over another entity.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.